[FEAT-UI/API]: Remove the ability for users to create duplicate PSE's
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
Research direction
Start by locating the PSE creation flow in the UI/API and reviewing the existing Hydro, LCG, and Reach implementations for their conventions. Done means users cannot create a PSE with a duplicate name through the relevant creation flow.
Written by the indexing model from the issue text.
Description
Simple:
- PSE can have the same name
- Make sure they cannot
- Follow the same conventions as other code (Hydro, LCG, Reach, etc)
- Dominant language
- No language data
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
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.
More from USACE/chart-docs
-
3SP
USACE/chart-docs#745 · 1 assignee ·
-
2SP
USACE/chart-docs#744 · 3 comments · 1 assignee ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
USACE/chart-docs#743 ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
USACE/chart-docs#742 ·
-
1SP
USACE/chart-docs#741 · 1 assignee ·
All issues in USACE/chart-docs
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
use-agent-os/agent-os#3312 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
needs-acceptance wg/data-plane-networking
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
vllm-project/semantic-router#4024 · 1 comment ·
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
amponce/archive-movie-browser#165 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100