Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

.editorconfig file validation #112

Open
FrediKats opened this issue May 17, 2024 · 0 comments
Open

.editorconfig file validation #112

FrediKats opened this issue May 17, 2024 · 0 comments
Labels
feature Use cases and global aim

Comments

@FrediKats
Copy link
Member

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
@FrediKats FrediKats added the feature Use cases and global aim label May 17, 2024
@github-project-automation github-project-automation bot moved this to Ideas/Not planned in Kysect task management May 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Use cases and global aim
Projects
Status: Ideas/Not planned
Development

No branches or pull requests

1 participant