You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Setup an Election
- Election should have status New, Open, Closed
- Election should have Manifest (can be empty)
- Election should have Key (can be empty)
- Election should have Name (essentially nickname or alias, perhaps that better name) that can be empty.
Edit an Election
Name, Manifest, Key can be edited when in New state only
Should be able to pull list of elections, get a single election as well.
using the new python 1.3 update
Possible Implementation
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered:
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
* fix typo
* Adds support for a V2 of the API
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
* Fix failing integration tests
* Rename folder to v1_1 per PR Feedback
* Rename the new endpoints from v2 to v1.1 per PR feedback
* Fix unused imports
Co-authored-by: Keith Fung <keithrfung@users.noreply.github.com>
Is there an existing issue for this?
Suggestion
Build the API's for:
- Election should have status
New
,Open
,Closed
- Election should have Manifest (can be empty)
- Election should have Key (can be empty)
- Election should have Name (essentially nickname or alias, perhaps that better name) that can be empty.
using the new python 1.3 update
Possible Implementation
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: