.editorconfig file validation
Open
Nobody has claimed this yet.
feature
- Dominant language
- C#
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Need to implement two level of validaton:
- Syntax level to ensure that document can be parsed. Some samples of invalid document:
- [category withoth ending bracket
- key = = =
- = value
- .NET .editorconfig semantic validation:
- Do duplicates
- Correct rule ID
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
Start by locating the existing .editorconfig parsing and validation entry points in the repository. Implement syntax checks for the listed malformed inputs and .NET semantic checks for duplicate rules and rule IDs; done means invalid files are reported clearly while valid files pass validation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100