BeaconCMS/beacon

Components - validate unique name per site

Open

#650 opened on Nov 13, 2024

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Elixir (120 forks)batch import
area:contentchoregood first issue

Repository metrics

Stars
 (1,194 stars)
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
Locate the schema for Components in the lib directory. Add a unique index on [:site id, :name] in a new migration. Ensure you run `mix ecto.gen.migration add unique constraint for components` and implement the change.
Tech stack
elixir
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitElixir
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75