req: Support URI Template
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- compilers
Research direction
The issue does not name files, tests, or an entry point. Start by reading the repository's lexer and parser entry points, then identify how URI components are currently extracted and where URI Template syntax would fit. Before coding, clarify the expected handling of template expressions and braces, and define tests that show when support is complete.
Written by the indexing model from the issue text.
Description
URI Template is being use in MCP. supporting extracting, so maybe need to specifically identify { and } still have to think about it.
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 0
- Avg merge
- 2m
- Merged PRs (30d)
- 2
Contributor 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 taskade/uri-parser
-
taskade/uri-parser#3 · 1 reaction · 2 assignees ·
All issues in taskade/uri-parser
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
area:tools bug good first issue help wanted priority:P2
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
TaewoooPark/Motifcode#14 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
newrelic-experimental/preflight#793 · 1 comment ·
-
bug 🐞
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
[Bounty proposal] fix(web): memory insights count an evening memory on the next day ($25 proposed) Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
BasedHardware/omi#15320 ·