[Bug] - Schema, colons when creating id cause problems
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 20/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- web-dev
Research direction
No file, test, or entry point is named; the only concrete artifact is the attached screenshot. Start by locating the schema ID creation path and reproducing the reported case with colons, then clarify the expected behavior from the reporter. Done means the colon-containing ID no longer causes the reported problem and the behavior is documented or covered by the project’s existing checks.
Written by the indexing model from the issue text.
Description
Description
Steps to Replicate
Additional context
Page occured:
Expected behavior
Artifacts (if appropriate):
- Dominant language
- JavaScript
- Stars
- 27
- Forks
- 14
- Avg merge
- 5d 22h
- Merged PRs (30d)
- 2
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing 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.
More from ORNL/DataFed
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
Type: Docs - User
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
Type: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 69/100
Maintainers usually reply within 1 day
-
bug ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
nearform/unbreakci#897 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
automation chore ci-cd consistency developer-experience difficulty: easy discoverability documentation enhancement github-actions good first issue help wanted hygiene priority: P3 seo shell yaml
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
swc-project/swc-next-issues#394 ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
githubnext/gh-aw-workshop#5790 ·
Maintainers usually reply within 1 day