Components - validate unique name per site
Open
area:content
chore
good first issue
- Dominant language
- Elixir
- Stars
- 1.3k
- Forks
- 134
- PR merge metrics
- No merged PRs in 30d
Description
Add a `unique_constraint` to `[:site, :name]` to avoid compilation issues. We do not support function overloading.
Contributor guide
Research direction
No file or test is named in the issue. Start by locating the Components data definition and its existing constraints, then inspect the related compilation path; done means component names are unique within a site and the compilation issue is avoided.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100