-
Notifications
You must be signed in to change notification settings - Fork 3
Refactor date/time parsing for mitpe events #1840
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
Merged
Merged
Changes from all commits
Commits
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 hidden or 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 hidden or 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 hidden or 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 hidden or 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
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.
This does not seem to get the correct time 100% of the time. For example
start_date_str="2020-01-28"
end_date_str="2020-01-28"
time_range_str="2-3:00pm"
returns start_date = datetime.datetime(2020, 1, 28, 2, 0)
end_date = datetime.datetime(2020, 1, 28, 15, 0)
before the conversion to utc
Also some events just have a start date like "1pm" and the time isn't parsed at all in that case
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.
Some events also have time strings that are going to be really hard to parse like "8:00pm; doors open at 7:30pm" I wonder if it makes sense to give up, store event dates then store event time as a string so it's displayed the way it was in the original listing
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.
Maybe I was trying too hard to get the times right; what's most important is really the start date because that's the only thing that's actually shown on the frontend. Next most important is end_date, because both are used to determine if the event should be published (start date or end date should be < now). If the professional ed api is sending back dates like "1 pm", that's just bad data and on them to fix.
How about I make sure the dates are correctly parsed (assuming the data is good), then for times, if it can't figure it out, it will just default to noon? That way when the pipeline runs in the early AM, it will keep events happening that day published for display.