Starting a new branch
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- Half a day
- Newbie friendliness
- 73/100
Research direction
Start by reading the existing StartBranch(string token, IState<T> state) overload and the StringTransition API it should accept. Then add the overload that takes a transition, mirroring how existing branch-starting code threads state through. Add tests covering a transition with a pattern such as test|Test|TEST, and update the documentation that mentions StartBranch. Done means the new overload is usable as shown, with tests and docs updated.
Written by the indexing model from the issue text.
Description
What we can do now
To start a branch, we use the method StartBranch(string token, IState<T> state)
The problem
If we want to start a branch from different tokens, we need to use this method again and again for similar tokens
For example
parser.StartBranch("test", state);
parser.StartBranch("Test", state);
parser.StartBranch("TEST", state);
The solution
Surcharche the method to also accept a transition. Since StringTransition can handle a regular expression, the above example can become
parser.StartBranch(new StringTransition(state).AddPattern("test|Test|TEST"))
Like always, don't forget to add tests and documentation
- Dominant language
- C#
- Stars
- 0
- Forks
- 0
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 5
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 Natvs/Nt.SyntaxParser
-
New light syntaxOpengood first issue usability
Difficulty 3/5 1-2 days Newbie friendliness 48/100
Natvs/Nt.SyntaxParser#45 ·
-
documentation
Difficulty 3/5 1-2 days Newbie friendliness 55/100
Natvs/Nt.SyntaxParser#35 ·
-
bug invalid
Difficulty 5/5 Over a week Newbie friendliness 20/100
Natvs/Nt.SyntaxParser#29 ·
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 20/100
Natvs/Nt.SyntaxParser#28 ·
-
enhancement good first issue
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Natvs/Nt.SyntaxParser#15 ·
All issues in Natvs/Nt.SyntaxParser
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Natvs/Nt.Automaton#33 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
a-corriger documentation
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
christian-raj/S-Aloha#312 ·
-
ready-for-agent tech-debt
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
DigiBanks99/menlo#640 ·
Maintainers usually reply within 1 day
-
ci
Difficulty 1/5 Under an hour Newbie friendliness 62/100
OpenTabletDriver/OpenTabletDriver#5283 ·
Maintainers usually reply within 3 days