Fix CLI group create command to require all mandatory fields #102
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
The CLI
group create
command was not enforcing all required fields at the command line level, allowing users to create event receiver groups without providing mandatory parameters. This could lead to confusing error messages from the backend validation rather than clear upfront validation.According to the issue requirements, all Event Receiver Groups must have these required fields:
name: String!
type: String!
version: String!
description: String!
enabled: Boolean!
event_receiver_ids: [ID!]!
Changes
Updated
cli/cmd/group/create.go
to markversion
andenabled
flags as required, matching the backend validation requirements.Before:
After:
Testing
--enabled=true
and--enabled=false
The fix ensures users get immediate, clear feedback about missing required parameters rather than cryptic backend errors.
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.