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

Add enum types valuemust be the same across source schemas #42

Open
wants to merge 7 commits into
base: main
Choose a base branch
from

Conversation

PascalSenn
Copy link
Contributor

No description provided.

**Explanatory Text**

This rule ensures that enum types with the same name across different source schemas in a composite schema have identical sets of values.
Enums, must be consistent across source schemas to avoid conflicts and ambiguities in the composite schema.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

At the moment enum value have to be strictly equal. We do not differentiate between output, input or combined enums

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

At the moment enum value have to be strictly equal

Do we plan to explore relaxing this to allow evolution of enums?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes we just talked about this in yesterdays wg, we are probably going to use the same pattern that federation uses currently.
union in ouput, intersection in input and exact match if used as in- and output

spec/Section 4 -- Composition.md Outdated Show resolved Hide resolved
spec/Section 4 -- Composition.md Outdated Show resolved Hide resolved
spec/Section 4 -- Composition.md Outdated Show resolved Hide resolved
@michaelstaib
Copy link
Member

Depending if the enum is uses only on the output, or only on the input or on both we have different handling of enums.

spec/Section 4 -- Composition.md Outdated Show resolved Hide resolved
spec/Section 4 -- Composition.md Outdated Show resolved Hide resolved
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants