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.
We currently have
fieldsRequiredByClientsto denote fields that would break clients if they were removed but we have no way to actually deprecate them.Add
fieldsDeprecatedForClientswhich behaves likefieldsRequiredByClientsi.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.