Replies: 7 comments 1 reply
|
@Edwinws Thanks for opening the issue. I can tell you from top of my head that it is due to TypeScript limitation. However, would you mind providing a somewhat real use-case to see if I can think of a way to support it? Personally, I haven't had the need to map Dictionary/Dynamic Object yet. |
|
@nartc Thanks for the response! The field stores a key-value pair that is received from another system via API call, and forwarded by the current system to another system via API call (the current system does not actually utilize it). Unfortunately, I do not know the full list of the keys, and they can change at any time. |
|
I see. I'll keep this one open and will think more about it. Since you have a workaround, I guess it's not too urgent. Thanks again for the issue. Feel free to chime in anything that you think it'd be helpful to get this supported. |
|
@Edwinws Did you find a solution to this? Our team is running into the same issue right now |
|
bump into this too,also automapper seems didn't support |
|
Similar issue here sending a dictionary from the backend to the frontend, it seems its not capable of handling it |
|
Hello @nartc |
Uh oh!
There was an error while loading. Please reload this page.
How do we go around automapping Indexable types?
I tried putting it into a class and using
@AutoMap({ typeFn: () => ParamClass })but it doesn't work.If it cannot work, what are the alternatives I can do if the keys are unknown? I can currently work around the problem by not automapping the field and perform a manual assignment after mapping.
All reactions