Validation consistency for condition names & references
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 35
- Forks
- 17
- Avg merge
- 48m
- Merged PRs (30d)
- 10
Description
Go through:
- https://github.com/openfga/api/blob/c96ec773cae9caf2a9536856bf1fa206a42ef7ef/openfga/v1/openfga.proto#L92
- https://github.com/openfga/api/blob/c96ec773cae9caf2a9536856bf1fa206a42ef7ef/openfga/v1/authzmodel.proto#L137
- https://github.com/openfga/language/blob/main/pkg/go/validation/validation-rules.go#L13
And make sure the validation is consistent for all three? Let's make it {1,50}
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the three referenced locations: openfga/v1/openfga.proto, openfga/v1/authzmodel.proto, and pkg/go/validation/validation-rules.go. Compare the condition-name and reference validation rules across them, then make all three enforce the requested {1,50} range. Confirm that the validation behavior is consistent across the referenced definitions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend-api-design
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100