Bert Loedeman

Hi Dima, thanks for using AutoMapperTS and locating this issue. Since a couple of months I am aware of this issue. Unfortunately, fixing this issue means quite some hassle, since...

I will look into it asap. I am currently quite busy at my day job, please be patient ;) . Of course, if you would like to solve the issue...

Hi @KlausHans, Thanks for reaching out. I am not aware of specific browser limitations. Based on what you suggest, could it be you did not actually load the profiles? AutoMapper...

That sure would help understanding the situation a lot! Of course, if you find a solution when creating a reproduction scenario, feel free to file a PR instead 😉. ________________________________...

Hi @lucaritossa , thanks for discovering this bug. Although it is 'valid' to produce this kind of functionality in JavaScript, I also tend to consider it a bug. I will...

Hi Matt, Could you please post your mapping code resulting in this exception? It would help investigating and/or clarifying the problem you are facing ;) ... Cheers, Bert

Hi @LWB-MatJ , @hirikarate and @gdovicak , I am unable to reproduce your issue using TypeScript. The TypeScript compiler compiles arrow functions to plain JavaScript functions at all times. At...

Hi @hirikarate and @gdovicak , Unfortunately, AutoMapperTS does not fully support ES2016 (yet). The workaround in this scenario is to use a classic EcmaScript 5 function (e.g. function(opts) { ......

I have the same error when importing the function in a TypeScript Angular application. There is another workaround I would like to add for those facing the same problem: `contrastColor.call({},...

For me as well 😢