From e5935473f61a171a3e74f83373fcc49f300fb1c9 Mon Sep 17 00:00:00 2001 From: chbk Date: Mon, 1 Feb 2021 15:03:48 +0100 Subject: [PATCH] Add link to "Syntax Naming Conventions" in "Creating a Grammar" --- content/hacking-atom/sections/creating-a-grammar.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/hacking-atom/sections/creating-a-grammar.md b/content/hacking-atom/sections/creating-a-grammar.md index a095acbf80..164479ec72 100644 --- a/content/hacking-atom/sections/creating-a-grammar.md +++ b/content/hacking-atom/sections/creating-a-grammar.md @@ -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.