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
Actual:
Suppose a schema contained a component called MyOperation, and an operation with ID My. Then Lily would generate base.package.MyOperation from the component as well as base.package.MyOperation from the operation, causing undefined behavior.
Expected:
All types should be given distinct FQNs in all scenarios. For example, Lily could generate base.package.component.schema.MyOperation, and a base.package.operation.MyOperation, though there are many other solutions.
Notes
Components are generated to the base package, so they can collide with Api, operation groups (including EveryOperation and EveryUntaggedOperation), and anything else also generated directly to the root.
The text was updated successfully, but these errors were encountered:
Tomboyo
changed the title
Potential name collision between components and operations
Potential name collision between components and operations (and others)
Jun 20, 2023
Actual:
Suppose a schema contained a component called
MyOperation
, and an operation with IDMy
. Then Lily would generate base.package.MyOperation from the component as well as base.package.MyOperation from the operation, causing undefined behavior.Expected:
All types should be given distinct FQNs in all scenarios. For example, Lily could generate base.package.component.schema.MyOperation, and a base.package.operation.MyOperation, though there are many other solutions.
Notes
Components are generated to the base package, so they can collide with Api, operation groups (including EveryOperation and EveryUntaggedOperation), and anything else also generated directly to the root.
The text was updated successfully, but these errors were encountered: