-
-
Notifications
You must be signed in to change notification settings - Fork 4
Open
Labels
π docsImprovements or additions to documentationImprovements or additions to documentation
Description
This came up in #339 but the diagnostic codes are not documented anywhere, you have to look in the source to see them:
django-language-server/crates/djls-ide/src/diagnostics.rs
Lines 70 to 81 in d5d43ad
| fn diagnostic_code(&self) -> &'static str { | |
| match self { | |
| ValidationError::UnclosedTag { .. } => "S100", | |
| ValidationError::UnbalancedStructure { .. } => "S101", | |
| ValidationError::OrphanedTag { .. } => "S102", | |
| ValidationError::UnmatchedBlockName { .. } => "S103", | |
| ValidationError::MissingRequiredArguments { .. } | |
| | ValidationError::MissingArgument { .. } => "S104", | |
| ValidationError::TooManyArguments { .. } => "S105", | |
| ValidationError::InvalidLiteralArgument { .. } => "S106", | |
| ValidationError::InvalidArgumentChoice { .. } => "S107", | |
| } |
There should be either a page with all of them listed (like djlint has for it's codes), or maybe like ruff a dedicated page for each code. Dedicated pages would be a bit more work, but probably worth it in the long run? Linkability and being able to provide examples -- though I suppose you could achieve that with a single page too, so π€·.
Metadata
Metadata
Assignees
Labels
π docsImprovements or additions to documentationImprovements or additions to documentation
Projects
Status
π Backlog