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

Potential name collision between components and operations (and others) #80

Open
Tomboyo opened this issue Jun 19, 2023 · 0 comments
Open

Comments

@Tomboyo
Copy link
Owner

Tomboyo commented Jun 19, 2023

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.

@Tomboyo Tomboyo changed the title Potential name collision between components and operations Potential name collision between components and operations (and others) Jun 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

1 participant