-
Notifications
You must be signed in to change notification settings - Fork 31
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 Instant
instead of ZonedDateTime
for Point.time
property
#125
Comments
jenetics
added a commit
that referenced
this issue
Jan 22, 2022
jenetics
added a commit
that referenced
this issue
Jan 22, 2022
jenetics
added a commit
that referenced
this issue
Jan 22, 2022
jenetics
added a commit
that referenced
this issue
Jan 22, 2022
jenetics
added a commit
that referenced
this issue
Jan 22, 2022
jenetics
added a commit
that referenced
this issue
Jan 22, 2022
jenetics
added a commit
that referenced
this issue
Jan 22, 2022
jenetics
added a commit
that referenced
this issue
Jan 22, 2022
#125: Using 'Instant' for timestamps
Merged into r3.0.0 branch. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The
Point.time()
property currently uses aZonedDateTime
for storing the time. This should be replaced by theInstant
class, which represents the type in the GPX file more accurately.At a first step, the used accessors and construtors should be marked as deprecated.
The text was updated successfully, but these errors were encountered: