Feature Request: function to detect a valid Token
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
Research direction
Start by reviewing httpsfv's existing token parsing and serialization entry points. Add a public way to determine whether a Go string is a valid RFC token, and verify that valid and invalid token strings are distinguished consistently with the library's existing behavior.
Written by the indexing model from the issue text.
Description
I have a case where the RFC I'm implementing defines a value as "either a String or a Token". I suppose I could always use String, but it would be nice to have a function in httpsfv to tell me whether a Go string is a valid Token so that I could cast it accordingly.
- Dominant language
- Go
- Stars
- 75
- Forks
- 11
- Avg merge
- 7d 11h
- Merged PRs (30d)
- 1
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.
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
enhancement needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
kind/cleanup
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
kubernetes-sigs/kueue#15947 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sympozium-ai/sympozium#627 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100