nvim-treesitter/runtime/queries/cue/locals.scm

; Scopes
[
  (source_file)
  (field)
  (for_clause)
] @local.scope

; References
(identifier) @local.reference

; Definitions
(import_spec
  path: (string) @local.definition.import)

(field
  (label
    (identifier) @local.definition.field))

(package_identifier) @local.definition.namespace

(for_clause
  (identifier) @local.definition.var
  (expression))

(for_clause
  (identifier)
  (identifier) @local.definition.var
  (expression))

(let_clause
  (identifier) @local.definition.var)
feat: add cue 2023-03-04 04:31:11 -05:00			`; Scopes`
			`[`
			`(source_file)`
			`(field)`
			`(for_clause)`
feat(locals)!: switch to upstream captures 2023-07-22 15:29:32 +02:00			`] @local.scope`
feat: add cue 2023-03-04 04:31:11 -05:00
			`; References`
feat(locals)!: switch to upstream captures 2023-07-22 15:29:32 +02:00			`(identifier) @local.reference`
feat: add cue 2023-03-04 04:31:11 -05:00
			`; Definitions`
			`(import_spec`
feat(locals)!: switch to upstream captures 2023-07-22 15:29:32 +02:00			`path: (string) @local.definition.import)`
feat: add cue 2023-03-04 04:31:11 -05:00
			`(field`
			`(label`
chore: query formatting 2024-01-06 15:05:50 +09:00			`(identifier) @local.definition.field))`
feat: add cue 2023-03-04 04:31:11 -05:00
feat(locals)!: switch to upstream captures 2023-07-22 15:29:32 +02:00			`(package_identifier) @local.definition.namespace`
feat: add cue 2023-03-04 04:31:11 -05:00
			`(for_clause`
feat(highlights)!: enforce documented captures (#6232) Problem: Allowing undocumented "secret" (sub)captures makes it harder to write comprehensive colorschemes and catch inconsistent captures. Solution: Only allow captures listed in CONTRIBUTING.md. Add useful (cross-language) subcaptures and drop language-specific or too niche ones. Follow-up: Adding further `*.builtin` captures and changing queries to use them. Language-specific subcaptures should instead be added in user config or a custom language plugin. 2024-03-03 11:00:11 +01:00			`(identifier) @local.definition.var`
feat: add cue 2023-03-04 04:31:11 -05:00			`(expression))`

			`(for_clause`
			`(identifier)`
feat(highlights)!: enforce documented captures (#6232) Problem: Allowing undocumented "secret" (sub)captures makes it harder to write comprehensive colorschemes and catch inconsistent captures. Solution: Only allow captures listed in CONTRIBUTING.md. Add useful (cross-language) subcaptures and drop language-specific or too niche ones. Follow-up: Adding further `*.builtin` captures and changing queries to use them. Language-specific subcaptures should instead be added in user config or a custom language plugin. 2024-03-03 11:00:11 +01:00			`(identifier) @local.definition.var`
feat: add cue 2023-03-04 04:31:11 -05:00			`(expression))`

			`(let_clause`
feat(highlights)!: enforce documented captures (#6232) Problem: Allowing undocumented "secret" (sub)captures makes it harder to write comprehensive colorschemes and catch inconsistent captures. Solution: Only allow captures listed in CONTRIBUTING.md. Add useful (cross-language) subcaptures and drop language-specific or too niche ones. Follow-up: Adding further `*.builtin` captures and changing queries to use them. Language-specific subcaptures should instead be added in user config or a custom language plugin. 2024-03-03 11:00:11 +01:00			`(identifier) @local.definition.var)`