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

[API Compat] Adding a new value to a public enum is not detected as a breaking change #45929

Open
bitbonk opened this issue Jan 13, 2025 · 1 comment
Labels
Area-ApiCompat untriaged Request triage from a team member

Comments

@bitbonk
Copy link

bitbonk commented Jan 13, 2025

Is your feature request related to a problem? Please describe.

When adding a new value to an existing public enum, these changes are not detected as a source breaking changes by the baseline package validator. Such changes are not source compatible because consuming code would need to be adjusted to account for the new value, for example in a switch statement.

Describe the solution you'd like

Introduce a new validation check that fails when a new value to an existing public enum was added.

@dotnet-issue-labeler dotnet-issue-labeler bot added Area-ApiCompat untriaged Request triage from a team member labels Jan 13, 2025
Copy link
Contributor

@dotnet/area-infrastructure-libraries a new issue has been filed in the ApiCompat area, please triage

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-ApiCompat untriaged Request triage from a team member
Projects
None yet
Development

No branches or pull requests

1 participant