microsoft / microsoft/vscode-css-languageservice
Property autocomplete + syntax highlighting does not trigger inside custom directive blocks
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 384
- Forks
- 217
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 14
Description
If you add a new directive to CSS custom data, autocomplete + syntax highlighting does not work within blocks defined by the directive. Mixins are one example where this would be useful:
@define-mixin sr-only {
position: absolute;
width: 1px;
height: 1px;
padding: 0;
margin: -1px;
overflow: hidden;
clip: rect(0, 0, 0, 0);
white-space: nowrap;
border-width: 0;
}
While this behavior may not be desirable for all directives, it'd be nice to have this as an option for some of them.
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 with docs/customData.md and the custom directive behavior described in the issue. Trace how directive blocks affect property autocomplete and syntax highlighting, then identify the existing coverage for those features; done means selected custom directives can opt into both behaviors without changing directives where that behavior is undesirable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css, typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100