Order columns should be set to notnull
Open
Nobody has claimed this yet.
1. to develop
backend
feature: stacks
technical debt
- Dominant language
- JavaScript
- Stars
- 1.4k
- Forks
- 354
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 43
Description
Some hardening from https://github.com/stefan-niedermann/nextcloud-deck/issues/465
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 by reading the linked nextcloud-deck issue #465, then locate the schema or migration that defines the order columns. Confirm which columns are intended to be non-null and verify that the resulting migration or schema change applies cleanly.
Written by the indexing model from the issue text.
Assessment
- Domain
- database
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100