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

Use field label modifier on deprecated #90

Merged
merged 1 commit into from
Oct 16, 2024

Conversation

josephsumabat
Copy link
Contributor

@josephsumabat josephsumabat commented Oct 16, 2024

This was previously not applying the field label modifier - fixes that issue.

Copy link
Collaborator

@chiroptical chiroptical left a comment

Choose a reason for hiding this comment

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

LGTM, minor question related to ensuring the deprecated field is actually part of the record.

It is possible, we explicitly don't want that which is fine imo.

, omitFields = const Discard
, deprecatedFields = [("field1", Just "Deprecated since build 500")]
, deprecatedFields = [("testField1", Just "Deprecated since build 500")]
Copy link
Collaborator

Choose a reason for hiding this comment

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

It isn't obvious, but do we require testField1 to exist?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

If required fields are included we check testField1 is one of the required fields if deprecated. We don't check that it isn't a part of omitFields though it might make sense to add that (I can do it as part of another PR)

@josephsumabat josephsumabat merged commit 326f061 into master Oct 16, 2024
22 checks passed
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.

3 participants