GLSP-1682: Repoint stale links to glsp-core - #113
Merged
Merged
Conversation
- Rewrite all deep links into glsp-client, glsp-server-node and their packages to their new home in glsp-core, accounting for the changed package layout (client/client, common/protocol, server/server, server/graph, server/server-mcp) - Apply a consistent link depth: landing-page component and integration cards point at the group directory (packages/client, packages/server), documentation prose at the concrete package it describes - Replace the SHA-pinned tool-palette link with a link to main and adapt the surrounding prose: the palette is now opened in the 'postRequestModel' startup hook, not 'preRequestModel' - Introduce glsp-core on the landing page as the consolidated home of client, Node server, protocol and shared tooling, and link the Node server framework and the protocol sources from the component cards - Point the workflow standalone example at examples/workflow-standalone in glsp-core, which also fixes the pre-existing wrong link to glsp-theia-integration Also: - Point the Protocol card at the site's own protocol documentation, since PROTOCOL.md in the umbrella repo is now only a stub redirecting here - Link the tool palette UI extension in the ui-extensions bullet list to its implementation instead of the protocol action definitions, matching the sibling Sprotty bullets - Use the canonical glsp-website-source URL for the documentation repository instead of relying on the eclipsesource redirect Part of: eclipse-glsp/glsp#1682
Contributor
|
Website preview removed, the pull request is closed. |
haydar-metin
approved these changes
Sep 18, 2026
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
2 participants
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.
What it does
The GLSP-1682 consolidation moved
glsp-clientandglsp-server-nodeintoeclipse-glsp/glsp-core. The website still linked the old repos exclusivelyand did not mention glsp-core at all.
layout (
client/client,common/protocol,server/server,server/graph,server/server-mcp)main, and adapt theprose: the palette now opens in
postRequestModel, notpreRequestModelNode server, protocol and shared tooling
Also:
PROTOCOL.mdin theumbrella repo is now just a stub redirecting here
Links to
eclipse-glsp/glspfor issues, discussions andPROTOCOL.mdareleft untouched.
Part of: eclipse-glsp/glsp#1682
How to test
grep -rn 'glsp-client\|glsp-server-node' content/— remaining hits areprose about the adopter's own
your-glsp-clientpackagemainFollow-ups
Changelog