Skip to content
This repository has been archived by the owner on Dec 15, 2022. It is now read-only.

Commit

Permalink
Add link to "Syntax Naming Conventions" in "Creating a Grammar"
Browse files Browse the repository at this point in the history
  • Loading branch information
chbk committed Apr 28, 2021
1 parent 2ccd709 commit f493c59
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion content/hacking-atom/sections/creating-a-grammar.md
Original file line number Diff line number Diff line change
Expand Up @@ -90,7 +90,7 @@ scopes:
'call_expression > identifier': 'entity.function.call'
```

This entry means that, in the syntax tree, any `identifier` node whose parent is a `call_expression` should be highlighted using three classes: `syntax--entity`, `syntax--function`, and `syntax--call`.
This entry means that, in the syntax tree, any `identifier` node whose parent is a `call_expression` should be highlighted using three classes: `syntax--entity`, `syntax--function`, and `syntax--call`. For a list of conventional classes, see the [Syntax Naming Conventions](../syntax-naming-conventions/) section.

Note that in this selector, we're using the [immediate child combinator](https://developer.mozilla.org/en-US/docs/Web/CSS/Child_selectors) (`>`). Arbitrary descendant selectors without this combinator (for example `'call_expression identifier'`, which would match any `identifier` occurring anywhere within a `call_expression`) are currently not supported.

Expand Down

0 comments on commit f493c59

Please sign in to comment.