fix parser: use context extend from nodes.util #1403
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Replace local
context_extendwithnodes.util.snippet_extend_contextThe default extend behavior was inconsistent between the functions (
ls.snippetandls.parser.parse_snippet/ls.parser.parse_snipmate)Previously, when passing a string as the first argument (context), the parser ignored the 'extend' parameters (while
ls.snippetnot). The localcontext_extendfunction did not merge extend fields if context was a string. Now, usingnodes.util.snippet_extend_contextensures that extend parameters are correctly merged regardless of whether context is a string or a table.