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
we generate objects named Foo1 and Foo2 in the same package as Foo (per sealed interface rules about packages -v- Java 9 modules). If the order of those two elements changes in a subsequent release of the OAS, then existing code will break: Lily will still generate objects named Foo1 and Foo2, but Foo1 will have property b, not a.
Consider implementing some kind of hash-like function which produces no collisions and is not dependent on element order so that we can create unique names for anonymous schemas that work between releases of the OAS and do not cause name collisions.
The text was updated successfully, but these errors were encountered:
Given a OneOf schema with anonymous (in-line) schemas in it like the following,
we generate objects named Foo1 and Foo2 in the same package as Foo (per sealed interface rules about packages -v- Java 9 modules). If the order of those two elements changes in a subsequent release of the OAS, then existing code will break: Lily will still generate objects named Foo1 and Foo2, but Foo1 will have property b, not a.
Consider implementing some kind of hash-like function which produces no collisions and is not dependent on element order so that we can create unique names for anonymous schemas that work between releases of the OAS and do not cause name collisions.
The text was updated successfully, but these errors were encountered: