Make collection name unique at a project level
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 296
- Forks
- 86
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 50
Description
Currently, we enforce uniqueness for collection names at an instance level but it would be great to keep the uniqueness at that project level. No two collections in a project should have the same name but two or more collections in an OpenFn instance can have the same name.
When sharing a collection with another project, we should block the share if the receiving project has a collection that has the same name as the shared collection.
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
Start by tracing collection creation and the project-sharing flow in the Elixir application, focusing on where collection-name uniqueness is currently enforced at the instance level. Done means duplicate names are rejected within one project while remaining allowed across projects, and sharing is blocked when the receiving project already has a collection with that name; add or update tests for both cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100