luckyframework / luckyframework/website
Clarify "autogenerated" option for columns
Nobody has claimed this yet.
- Dominant language
- Crystal
- Stars
- 39
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Description
If your column gets a default value from the database, you need to use the `autogenerated: true` column option or specify a default value in Crystal...
```crystal
column admin : Bool, autogenerated: true
# or
column admin : Bool = false
```
If you don't specify one of these, then when trying to save through an operation, you'll get an error about a missing column unless you pass in a value.
We should add more documentation about this.
Contributor guide
No contributing guide indexed for this repository
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
No documentation file or entry point is named. Start by locating the documentation for column options, then clarify how database defaults relate to `autogenerated: true`, Crystal defaults, and missing-column errors; done means readers can tell when each option is required.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- crystal
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100