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

Localized DateTime ambiguous handling #131

Open
maennchen opened this issue Feb 27, 2024 · 0 comments · May be fixed by #133
Open

Localized DateTime ambiguous handling #131

maennchen opened this issue Feb 27, 2024 · 0 comments · May be fixed by #133

Comments

@maennchen
Copy link
Owner

maennchen commented Feb 27, 2024

          > does that mean most functions in DateHelper need to return either one or two dates?

Probably not:

If you have the setting on both, we can just return the first occurrence. When we look for the next candidate date, we should automatically reach the later occurrence.

So the logic could be something like this:

  • if result ambiguous and setting is earlier: return earlier
  • if result ambiguous and setting is later: return later
  • if result ambiguous and setting is both: return earlier or later depending on adjusted

Originally posted by @maennchen in #129 (comment)

Needed for quantum-elixir/quantum-core#407

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant