Skip to content

Figure out Which Schema is Getting Turned into ModelError #95

@boyleconnor

Description

@boyleconnor

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions