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

Handle conflicting fields when resolving parsed objects #8

Open
erikc5000 opened this issue Oct 28, 2019 · 0 comments
Open

Handle conflicting fields when resolving parsed objects #8

erikc5000 opened this issue Oct 28, 2019 · 0 comments
Labels
design Design issue/question enhancement New feature or request
Milestone

Comments

@erikc5000
Copy link
Owner

Right now, if a DateTime parser provides both DAY_OF_MONTH and DAY_OF_YEAR, it'll just take the day of month value first assuming it has a year and month. But the day of year value may conflict or otherwise be indicative of a poorly defined custom parser.

This sort of behavior needs to looked at across all date-time primitives and may require more sophisticated resolution behavior.

@erikc5000 erikc5000 added enhancement New feature or request design Design issue/question labels Oct 28, 2019
@erikc5000 erikc5000 added this to the 0.7.0 milestone May 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
design Design issue/question enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant