-
Notifications
You must be signed in to change notification settings - Fork 460
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
Review date handling with header consolidation and date serialization in references #807
Merged
Merged
Changes from 7 commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
01b4d35
merge date with header consolidation, better date serialization in re…
kermitt2 5f86ee9
update naming
lfoppiano cc36bc3
add more tests on toIsoString
lfoppiano 25d8182
add more tests on toIsoString
lfoppiano c938eb8
Merge branch 'master' into follow-up-761
lfoppiano a953965
return date2 if date1's year is not valid
lfoppiano 1b73754
rewrite merge to have a new instance Date, avoid loosing some raw str…
kermitt2 b02dcd7
implements Comparable<Date> + cosmetics
lfoppiano 9a41c57
addition from #814
kermitt2 0bd69f0
update tests
kermitt2 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think
date
is preferred overyear
and if used,year
should only consist of a numeric year.I see two options here:
date
field.So, if a
normalized_publication_date
exists, use it as iso string, else if thepublication_date
exists use that.normalized_publication_date
as ISO string but use theyear
,month
andday
fields instead. This would ensure thatyear
,month
andday
are numeric and the (more detailed, with day ranges)publication_date
could be put as a string in thedate
field. If both are given, it is up to the user to decide which to keep.