-
Notifications
You must be signed in to change notification settings - Fork 232
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
Agency schema redux #238
Agency schema redux #238
Conversation
Apologies to keep moving the goalposts @ian-r-rose, but there's another round of changes that make this PR obsolete. I think we might push this to 0.3.2? We'd really like to cut 0.3.1 soon. |
b476d15
to
10a5c62
Compare
Note: the initial status of a vehicle during and event update is prescribed, but not enforced, to allow for asynchronous processing of updates.
10a5c62
to
c1740a5
Compare
Updated in light of #258, #249, #245. The API is getting rich enough that it's probably time to investigate using OpenAPI rather than pure JSONSchema to better document the responses that are possible from the Agency API. However, I think that's a big enough undertaking that it may be better for a follow-up. |
Looks good to me. Would like eyeballs on from @hunterowens and @toddapetersen. |
@Karcass this looks good to me. I can clean up, rebase and merge in? |
@hunterowens yep! |
Fixes #169.
Supersedes #172.
I have tried to follow the current
agency/README.md
indev
as closely as possible. If there are existing open PRs which I should also try to take into account, feel free to let me know.Also, this is not particularly well-tested in the absence of synthetic agency data, so there are likely some issues that will need to be ironed out, here or in follow-ups.