@hydranium/glsp-server 1.0.0-next.95 → 1.0.0-next.96

package/lib/state/reconciling-multi-document-glsp-state.d.ts

@@ -128,11 +128,11 @@ export declare class ReconcilingMultiDocumentGlspState<TRoot extends AstNode, TP
      *
      * **Skipping unchanged documents is correctness, not an optimisation.** A
      * write goes through `ModelService.update`, which re-serializes from the AST —
-     * so writing a document that did not change still rewrites its text, and a
-     * serializer is free to normalise formatting and cannot preserve comments.
-     * Persisting the whole write set unconditionally therefore means a pure layout
-     * drag reflows the semantic file and strips its comments, which is a data
-     * loss the user never asked for and would struggle to attribute.
+     * so writing a document that did not change still rewrites its text in the
+     * serializer's own layout. Persisting the whole write set unconditionally
+     * therefore means a pure layout drag reflows the semantic file, a change the
+     * user never asked for and would struggle to attribute. Comments survive that
+     * rewrite, but the hand-formatting around them does not.
      *
      * Compared by serialised form. Both sides come from the same encoder walking
      * the same shape, so key order is stable and a string compare is sound here;

package/lib/state/reconciling-multi-document-glsp-state.js

@@ -154,11 +154,11 @@ let ReconcilingMultiDocumentGlspState = class ReconcilingMultiDocumentGlspState
      *
      * **Skipping unchanged documents is correctness, not an optimisation.** A
      * write goes through `ModelService.update`, which re-serializes from the AST —
-     * so writing a document that did not change still rewrites its text, and a
-     * serializer is free to normalise formatting and cannot preserve comments.
-     * Persisting the whole write set unconditionally therefore means a pure layout
-     * drag reflows the semantic file and strips its comments, which is a data
-     * loss the user never asked for and would struggle to attribute.
+     * so writing a document that did not change still rewrites its text in the
+     * serializer's own layout. Persisting the whole write set unconditionally
+     * therefore means a pure layout drag reflows the semantic file, a change the
+     * user never asked for and would struggle to attribute. Comments survive that
+     * rewrite, but the hand-formatting around them does not.
      *
      * Compared by serialised form. Both sides come from the same encoder walking
      * the same shape, so key order is stable and a string compare is sound here;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hydranium/glsp-server",
-  "version": "1.0.0-next.95",
+  "version": "1.0.0-next.96",
   "description": "GLSP protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/data-server; built on @hydranium/core.",
   "keywords": [
     "hydranium",
@@ -87,9 +87,9 @@
   "devDependencies": {
     "@eclipse-glsp/protocol": "2.7.0",
     "@eclipse-glsp/server": "2.7.0",
-    "@hydranium/core": "1.0.0-next.95",
-    "@hydranium/langium": "1.0.0-next.95",
-    "@hydranium/protocol": "1.0.0-next.95",
+    "@hydranium/core": "1.0.0-next.96",
+    "@hydranium/langium": "1.0.0-next.96",
+    "@hydranium/protocol": "1.0.0-next.96",
     "inversify": "6.2.2",
     "reflect-metadata": "0.2.2",
     "rimraf": "^5.0.0",
@@ -100,9 +100,9 @@
   "peerDependencies": {
     "@eclipse-glsp/protocol": "^2.6.0",
     "@eclipse-glsp/server": "^2.6.0",
-    "@hydranium/core": "1.0.0-next.95",
-    "@hydranium/langium": "1.0.0-next.95",
-    "@hydranium/protocol": "1.0.0-next.95",
+    "@hydranium/core": "1.0.0-next.96",
+    "@hydranium/langium": "1.0.0-next.96",
+    "@hydranium/protocol": "1.0.0-next.96",
     "inversify": "^6.0.0",
     "reflect-metadata": "^0.2.2",
     "vscode-jsonrpc": "9.0.1",

package/src/state/reconciling-multi-document-glsp-state.ts

@@ -180,11 +180,11 @@ export class ReconcilingMultiDocumentGlspState<TRoot extends AstNode, TPrimary e
     *
     * **Skipping unchanged documents is correctness, not an optimisation.** A
     * write goes through `ModelService.update`, which re-serializes from the AST —
-    * so writing a document that did not change still rewrites its text, and a
-    * serializer is free to normalise formatting and cannot preserve comments.
-    * Persisting the whole write set unconditionally therefore means a pure layout
-    * drag reflows the semantic file and strips its comments, which is a data
-    * loss the user never asked for and would struggle to attribute.
+    * so writing a document that did not change still rewrites its text in the
+    * serializer's own layout. Persisting the whole write set unconditionally
+    * therefore means a pure layout drag reflows the semantic file, a change the
+    * user never asked for and would struggle to attribute. Comments survive that
+    * rewrite, but the hand-formatting around them does not.
     *
     * Compared by serialised form. Both sides come from the same encoder walking
     * the same shape, so key order is stable and a string compare is sound here;