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

Document how to determine a recurring event's ID #191

Open
kylecombes opened this issue Apr 28, 2018 · 2 comments
Open

Document how to determine a recurring event's ID #191

kylecombes opened this issue Apr 28, 2018 · 2 comments
Labels
api Issues that affect the ABE API clients

Comments

@kylecombes
Copy link
Contributor

The means by which rec_id is determined needs to be documented somewhere. Currently I (the front end) am unable to request data for a specific recurrence of a recurring event.

Old frontend code suggests that it should be possible to request data for a specific recurrence of a recurring event series by making a GET request of the form /events/<event_sid>/<ms_since_unix_epoc_of_recurrence>. However, submitting GET /events/5adfc5a48b17bd000cbb6b86/1524614451000 to the prod server results in

{ "message": "The requested URL was not found on the server.  If you entered the URL manually please check your spelling and try again." }

@newsch also suggested I try querying using the ISO 8601 date format, but that (yyyy-mm-dd) results in the same response.

@kylecombes kylecombes added the api Issues that affect the ABE API clients label Apr 28, 2018
@kylecombes kylecombes added this to the Final Events Ready milestone Apr 28, 2018
@kylecombes
Copy link
Contributor Author

Actually, it'd probably be preferable for the server to generate recId and include it on each recurrence object.

@kylecombes kylecombes added the blocking Blocks development on ABE or its associated projects label Apr 30, 2018
@kylecombes
Copy link
Contributor Author

It appears that the ISO 8601 format of YYYY-MM-DD works.

@kylecombes kylecombes removed the blocking Blocks development on ABE or its associated projects label May 3, 2018
@osteele osteele removed this from the Final Events Ready milestone May 15, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api Issues that affect the ABE API clients
Projects
None yet
Development

No branches or pull requests

2 participants