Extract code for parsing .editorconfig nodes and cover with more tests
Open
Nobody has claimed this yet.
refactoring
- Dominant language
- C#
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Need to be sure that parser code works okay in all expected scenarios. Probably, in some point of time we will rewrite for better performance. So, tests are required.
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.
Research direction
No source files, parser entry point, existing tests, or expected scenarios are named. Start by locating the .editorconfig node-parsing code and its current tests; done means the parsing code is extracted as intended and tests cover the expected scenarios.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100