Skip to content

Commit

Permalink
[CSS] Fix completions for property values when no characters have bee…
Browse files Browse the repository at this point in the history 
…n typed yet
  • Loading branch information
@wbond
wbond committed Dec 15, 2016
1 parent 6fa9698 commit c6393db
Showing 1 changed file with 4 additions and 2 deletions.
6 changes: 4 additions & 2 deletions CSS/CSS.sublime-syntax
View file
Expand Up @@ -614,9 +614,10 @@ contexts:
- match: \bfont(-family)?(?!-)\b
scope: support.type.property-name.css
push:
- match: (:)\s*
- match: (:)([ \t]*)
captures:
1: punctuation.separator.key-value.css
2: meta.property-value.css
push:
- meta_content_scope: meta.property-value.css
- match: '\s*(;)|(?=[})])'
Expand Down Expand Up @@ -708,9 +709,10 @@ contexts:
| symbols|speak-as|grid-gap|grid-row-gap
)\b
scope: support.type.property-name.css
- match: (:)\s*
- match: (:)([ \t]*)
captures:
1: punctuation.separator.key-value.css
2: meta.property-value.css
push:
- meta_content_scope: meta.property-value.css
- match: '\s*(;)|(?=[})])'
Expand Down

3 comments on commit c6393db

@FichteFoll
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any particular reason why you didn't remove the whitespace matches entirely?

@wbond
Copy link
Member Author

@wbond wbond commented on c6393db Dec 16, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not really. I suppose I probably could have taken the whitespace off of there and also in the pop rule.

@FichteFoll
Copy link
Collaborator

@FichteFoll FichteFoll commented on c6393db Dec 16, 2016 •
edited

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would also get rid of one line each when replacing captures with scope 👍

Please sign in to comment.