Add support for data values schema without defaults
- Dominant language
- Go
- Stars
- 1.9k
- Forks
- 167
- PR merge metrics
- No merged PRs in 30d
Description
**Describe the problem/challenge you have**
Some data values don't have sensible defaults and I'd like template users to always provide them
**Describe the solution you'd like**
Maybe special value for `@schema/default` annotation , which would indicate that there is no deafult value at all? Schema is then used to define just type of the value, expecting template user to always provide it.
**Anything else you would like to add:**
Currently it can be simulated with assert, but it is too verbose.
---
Vote on this request
This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.
👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"
We are also happy to receive and review Pull Requests if you want to help working on this issue.
Contributor guide
Research direction
Start by tracing how the `@schema/default` annotation and schema-defined data values are handled, using the existing `assert` workaround as a behavioral reference. Define how a schema marks a value as having no default, then verify that template users must provide it while its type remains enforced.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100