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

Deprecate field/method property discovery config values #2442

Closed
evanchooly opened this issue Jun 27, 2023 · 0 comments
Closed

Deprecate field/method property discovery config values #2442

evanchooly opened this issue Jun 27, 2023 · 0 comments
Labels
docs enhancement migration Issue contains updates that should be noted in a migration document
Milestone

Comments

@evanchooly
Copy link
Member

In prior versions, this made sense. In 3.0 such a distinction will be largely meaningless and so in the name of keeping things as simple and clean as possible, let's remove this config element. Mapping metadata will possible on both fields and accessors, however. Either/or should work and mixed usage in a project will be supported as well.

@evanchooly evanchooly added enhancement docs migration Issue contains updates that should be noted in a migration document labels Jun 27, 2023
@evanchooly evanchooly added this to the 2.4.0 milestone Jun 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs enhancement migration Issue contains updates that should be noted in a migration document
Projects
None yet
Development

No branches or pull requests

1 participant