-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Different Array<T> and Promise<T> types getting assigned the same metadata store id #33
Comments
I think I know what is going on. The arrays are the same ts.Symbol probably so they have the same id. tst-reflect/transformer/src/helpers.ts Lines 118 to 128 in f835710
In the new version I use type.id, not symbol.id, it should fix this issue, but it may cause other issues... Not every symbol has id but every type has. Only types with Id are stored, others are inlined... but it may not be an issue, but it will generate bigger metadata. |
Thanks, I'll play around and see if I can fix. |
I'm working on it. Return type's id instead of symbol's id is not enough. I've made several other changes to make it work, everything seems alright but two tests are failing. Those tests seems unrelated to this but idk there must be something,.. I'm trying to solve that. |
Solved. I've published |
Awesome, looks like the issue is fixed for me! |
@all-contributors please add @bjsi for bug report |
I've put up a pull request to add @bjsi! 🎉 |
I ran into an issue with using getType on arrays and promises.
I cloned the library and ran in debug mode inside the test suite:
I think the problem is that
string[]
andnumber[]
are getting assigned the same metadata store id.Let me know if I can help in any way, maybe this is already fixed in the update you are working on.
The text was updated successfully, but these errors were encountered: