-
Notifications
You must be signed in to change notification settings - Fork 28
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
API V2 #194
API V2 #194
Conversation
More specifically creates a single endpoint at PUT api/v2/election that doesn't currently do anything, but the routes are all there for more easily fleshing out #178
This pull request introduces 3 alerts when merging 6e30a2d into cbc7cc5 - view on LGTM.com new alerts:
|
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.
Please relabel to v1.1
We are trying to keep major version to align across the repositories.
V2 -> electionguard 2.0 , electionguard-python 2.0 etc.
This pull request introduces 3 alerts when merging ee0bceb into cbc7cc5 - view on LGTM.com new alerts:
|
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.
Issue
Starts #178
Description
This begins a V1.1 of the API in support of #178. It doesn't actually add anything of value yet other than a create election endpoint that doesn't do anything, but adding substantial V1.1 endpoints will be substantially easier after this work.
Testing
Try
PUT /api/v1.1/election
with{ "name": "Hamilton General Election" }
. It should return back a 200 with a success message, but it doesn't actually do anything just yet.