You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a user, when I try to compile an OAS document that has duplicate elements due to author error, Lily should warn me about the error (and tell me which generated types are impacted), but continue generating classes so that I can work with as much of the OAS that is well-formed as possible rather than be completely blocked.
This should also be the case when Lily decides to name an anonymous type in such a way that it collides with another type. Ideally this is logged at a more severe level than usual since it's a design flaw on our part, if possible.
The text was updated successfully, but these errors were encountered:
As a user, when I try to compile an OAS document that has duplicate elements due to author error, Lily should warn me about the error (and tell me which generated types are impacted), but continue generating classes so that I can work with as much of the OAS that is well-formed as possible rather than be completely blocked.
For example:
This should also be the case when Lily decides to name an anonymous type in such a way that it collides with another type. Ideally this is logged at a more severe level than usual since it's a design flaw on our part, if possible.
The text was updated successfully, but these errors were encountered: