A quick explanation on this - the old code was matching if the full
scope was ok. This is fine when we want to test a single grammar, but
for example, TextMate grammars always added `.ruby` on the last part of
the grammar. That was quite bad for TreeSitter, that basically didn't do
the same thing. So now it matches a fine crafted Regexp that basically
checks if the full scope is match from the beginning, OR if part of the
scope (up to just before the `.`) matches. So, for example, for
`constant.other.ruby` it'll match `constant`, `constant.other`, and
`constant.other.ruby` but it'll NOT MATCH `constant.oth`.
`LanguageLayer` is re-introduced. All tree parsing and querying will eventually need to live inside an instance of `LanguageLayer`. Right now, just the syntax highlighting is doing so.
Don't want those implicit values showing in the middle of suggested
auto-completions! Only at the end!
Return an empty array instead of the implicit values where needed,
if recursing.
Avoid appending the implicit values multiple times / in multiple
spots in the values list per property.
(These duplicate implicit values would be deduped, but the middle ones
would be the ones that would be kept, whereas we want to only keep
the bottom ones.)
---
Details:
The function that adds the implicit values to each property is
recursed sometimes, based on the structure of the data we are
ingesting. For the deeper/innner calls of this function, avoid
appending the implicit values, since we will be doing that at the end
of the outer/upper calls.
Makes sure the implicit values are not added in the middle *and* at
the bottom, in which scenario they would eventually be deduped
(removing the bottom copy, I suppose), but leaving one copy of the
implicit values smack-dab in the middle of the values list for the
given property.
We want only one copy of these values, sure, so deduping is
appreciated, but they should be *at the bottom* of the list of values.
Not the middle. So we gotta make sure the only copy fed through the
deduper function is the one at the bottom.
(This commit should just be re-arranging the values,
so as to put the implicit ones last.)
These implicit values are the same for all properties.
I find it more useful to view the property-specific values first,
since users may not actually know what property-specific values exist
for a given CSS property, and these implicit values are *always*
allowed... (I think they are, anyway).
This shows those property-specific values first, better advertising
what options are actually available to use. (Besides that, as far as I
know, the implicit "inherit", "initial", "unset" values are not as
commonly used as the property-specific values anyway.)
