You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Should ? (nullable type), | (union type) and & (intersection type) be have font-lock-operator-face or @font-lock-type-face. Currently font-lock-operator-face is going to be applied
Its value is 3
Decoration level to be used by tree-sitter fontifications.
Major modes categorize their fontification features into levels,
from 1 which is the absolute minimum, to 4 that yields the maximum
fontifications.
Level 1 usually contains only comments and definitions.
Level 2 usually adds keywords, strings, data types, etc.
Level 3 usually represents full-blown fontifications, including
assignments, constants, numbers and literals, etc.
Level 4 adds everything else that can be fontified: delimiters,
operators, brackets, punctuation, all functions, properties,
variables, etc.
The text was updated successfully, but these errors were encountered:
To track issues to resolve:
?
(nullable type),|
(union type) and&
(intersection type) be havefont-lock-operator-face
or@font-lock-type-face
. Currentlyfont-lock-operator-face
is going to be appliedCONST_NAME = 'value'
in class declaration instead of justCONST_NAME
highlight $ in variable name and object member #16${XX}
syntax as it's deprecated in 8.2https://wiki.php.net/rfc/deprecate_dollar_brace_string_interpolation
implements
and,
instead of just interface names highlight $ in variable name and object member #16;
( `expression_statement ";") in for is not highlighted$
in variable name highlight $ in variable name and object member #16this
in variable name update font rules, indention, faces and readme #68list
highlight $ in variable name and object member #16array
highlight $ in variable name and object member #16Missing keywords:
Rework
treesit-font-lock-feature-list
treesit-font-lock-level
here is a gist from the documentation: Align font lock levels built-in ts modes #19The text was updated successfully, but these errors were encountered: