-
Notifications
You must be signed in to change notification settings - Fork 83
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
schedule/feeds: make json feed schema compatible #1612
base: main
Are you sure you want to change the base?
Conversation
aef04d9
to
d94e2f3
Compare
d94e2f3
to
d70ab38
Compare
apps/schedule/feeds.py
Outdated
@@ -46,12 +49,146 @@ def schedule_json(year): | |||
return Response(json.dumps(schedule), mimetype="application/json") | |||
|
|||
|
|||
@schedule.route("/schedule/schedule-<int:year>.json") # TODO validate url with upstream |
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 we can just use /schedule/<int:year>.json
and merge this pull request after this years EMF?
also add request argument to show the old-style json schedule
abort(404) | ||
|
||
schedule = [_convert_time_to_str(p) for p in _get_scheduled_proposals(request.args)] | ||
if request.args.get('format') == 'array': |
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.
Also feels wrong to do it like this. I don't know. Feedback please! (I'm happy to expose the schema-compatible json on another endpoint, i just have no clue what would be a good name)
No description provided.