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.

Sign up for GitHub

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

Jump to bottom

Field deprecation #86

Open
chiroptical opened this issue Jun 3, 2024 · 0 comments
Open

Field deprecation #86

chiroptical opened this issue Jun 3, 2024 · 0 comments

Comments

@chiroptical
Copy link
Collaborator

We currently have fieldsRequiredByClients to denote fields that would break clients if they were removed but we have no way to actually deprecate them.

Add fieldsDeprecatedForClients which behaves like fieldsRequiredByClients i.e. they can't be removed. However, they don't generate code. That way, the clients can update the types, do the refactors, and then let the maintainer know the deprecated fields can be removed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@chiroptical