Michael Davis 060255344c syntax: Lookup up (#set! injection.language "name") props by ID ... This splits the `InjectionLanguageMarker::Name` into two: one that preforms the previous behavior (using the language configurations' `injection_regex` fields and performing a match) and a new variant that looks up directly by `language_id` with equality. The old variant is used when capturing the injection language like we do in the markdown queries for codefences. That captured text is part of the document being highlighted so we might need a regex to recognize a language like JavaScript as either "js" or "javascript". But the text passed in the `(#set! injection.language "name")` property can be looked up directly. This property is in the query code so there's no need to be flexible in what we accept: we can require that the `(#set! injection.language ..)` properties refer to languages by their configured ID. This should save a noticeable amount of work for the common case of injections: `(#set! injection.language)` is used much more often than `@injection.language`.		2025-01-23 11:01:35 +09:00
..
src	syntax: Lookup up (#set! injection.language "name") props by ID	2025-01-23 11:01:35 +09:00
tests	Resolve new Clippy lints	2024-05-07 15:15:52 -04:00
.gitignore	Initial import.	2020-05-20 18:14:51 +09:00
Cargo.toml	Use a workspace dependency for bitflags	2025-01-13 18:26:31 -05:00