Skip to content
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

Figure out Which Schema is Getting Turned into ModelError #95

Open
boyleconnor opened this issue Jun 7, 2021 · 0 comments
Open

Figure out Which Schema is Getting Turned into ModelError #95

boyleconnor opened this issue Jun 7, 2021 · 0 comments

Comments

@boyleconnor
Copy link
Collaborator

When generating the typescript-fetch client from the deidentifier schema, one of the models apparently has a name conflict with some internal type in TypeScript, leading to the following error (repeated several times when generating from schema):

[main] WARN  o.o.c.l.AbstractTypeScriptClientCodegen - Error (model name matches existing language type) cannot be used as a model name. Renamed to ModelError

This leads to creation of a file and class called ModelError.ts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant