-
Notifications
You must be signed in to change notification settings - Fork 12
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
[Bug Report] Error while running the program: RangeError: Maximum call stack size exceeded #246
Comments
Hi @JuncalLP, thanks for bringing that up. I need the metadata to reproduce this. Can you share the metadata file here? Otherwise invite me to a private repo if that's sensible information... |
I'm getting this same type of error. Metadata available via the public url in the config:
full call stack
|
Hi, thanks @d-a-s for the next example. @JuncalLP already provided me with one, but it's always good to have more 😄 Current Status QuoActually repeating what I've said in #251. The generation actually works fine when emitting TS, but as soon as this get's typechecked (tsc) or included in source code, the error occurs. The same happens when generating It seems that the types are too complex (see also microsoft/TypeScript#33460). I cannot find a bug in the code. Experiments with generating less to overcome the error have shown that it's more or less random what to leave out: As soon as the complexity is reduced it might work. Well, it leads me to the conclusion that the typing is just too complex... of course, I might be wrong here... My next solution approach: Generate an API model for the services. I suspect that TS has problems to use the generated services as types without already fully checking the service... |
I opened an issue with TypeScript: see microsoft/TypeScript#58439 |
Running generation with
Modes.all
and default config throwsThe XML is not large (250KB) but I suspect there are naming issues and complexities that might be causing this. Probably it's not fully an
odata2ts
issue, but I'd like to be able to pinpoint exactly what on the EDM is causing this.Saw #243 and updated to
0.32.0
hoping that automatic name clash resolution solved this, but still getting same output.Modes.qobjects
works as intended.The text was updated successfully, but these errors were encountered: