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

Explicitly specify invalid combinations of fields. #86

Merged
merged 1 commit into from
Aug 13, 2023

Conversation

robshakir
Copy link
Contributor

 * (M) doc/specification.md
 * (M) v1/proto/service/gribi.proto
  - Clarify explicitly that specifying more than one of `election_id`
    `params` and `operation` together is not valid. The specification
    implicitly said this before (`session_params` must be the only
    field in the first message, `election_id` must be the only field
    populated when updating an election ID, etc. This change makes this
    explicit.

 * (M) doc/specification.md
 * (M) v1/proto/service/gribi.proto
  - Clarify explicitly that specifying more than one of `election_id`
    `params` and `operation` together is not valid. The specification
    implicitly said this before (`session_params` must be the only
    field in the first message, `election_id` must be the only field
    populated when updating an election ID, etc. This change makes this
    explicit.
@robshakir robshakir merged commit c1af2b8 into master Aug 13, 2023
@robshakir robshakir deleted the invalid-combinations branch August 13, 2023 11:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants