Sync from umple-lsp@b0604a3 (grammar, v0.1.3)#2
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Auto-sync from umple-lsp
Source: umple-lsp@b0604a32b0278151b9453074fe1ddec6de7b0934
Change type:
grammar(grammar =grammar.js/parser.c, highlights =queries/**.scm)Version bump: 0.1.2 → 0.1.3
Changed paths in umple-lsp
Safe to merge?
highlightsonly — safe to merge now.grammarorboth— wait for anumple-lsp-servernpmpublish that includes matching server-side indexer support
before merging, if the new syntax requires it. Check the
latest published server with
npm view umple-lsp-server version.If you merge early, editor highlighting may understand new
syntax before the LSP does; users will see a temporary
feature gap until npm catches up.
Next steps after merge
umple-lsp-serverto npm if the serverchanged alongside this grammar.
pointer and
extensions.tomlumple entry version in a forkof
zed-industries/extensions, then opening a PR there.This stays manual by design (topic 040).
Produced by
.github/workflows/sync-umple-zed.ymlin umple-lsp.Re-runs on subsequent grammar / highlight pushes force-push onto
sync/umple-lsp-masterto coalesce with this PR instead of stacking new ones.