@hydranium/protocol 1.0.0-next.36 → 1.0.0-next.38

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -28,7 +28,7 @@
28
28
  * Nesting is a HOST convention, not the framework's: Theia flattens a nested
29
29
  * catalogue by joining keys with `/`, which is the separator a code already
30
30
  * uses, so an adopter on that host writes the file nested and one handed
31
- * straight to a `ServerMessageRenderer` writes it flat. Both end up here.
31
+ * straight to a `DefaultMessageRenderer` writes it flat. Both end up here.
32
32
  *
33
33
  * `_`-prefixed keys are dropped by PREFIX rather than by matching one literal
34
34
  * name, so a second note added to a file cannot silently become a catalogue
@@ -34,7 +34,7 @@ const primitives_1 = require("../messages/primitives");
34
34
  * Nesting is a HOST convention, not the framework's: Theia flattens a nested
35
35
  * catalogue by joining keys with `/`, which is the separator a code already
36
36
  * uses, so an adopter on that host writes the file nested and one handed
37
- * straight to a `ServerMessageRenderer` writes it flat. Both end up here.
37
+ * straight to a `DefaultMessageRenderer` writes it flat. Both end up here.
38
38
  *
39
39
  * `_`-prefixed keys are dropped by PREFIX rather than by matching one literal
40
40
  * name, so a second note added to a file cannot silently become a catalogue
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@hydranium/protocol",
3
- "version": "1.0.0-next.36",
3
+ "version": "1.0.0-next.38",
4
4
  "description": "Generic, language-agnostic types, constants, and pure utilities for the hydranium framework.",
5
5
  "keywords": [
6
6
  "hydranium",
@@ -32,7 +32,7 @@ import { collectMessages } from '../messages/primitives';
32
32
  * Nesting is a HOST convention, not the framework's: Theia flattens a nested
33
33
  * catalogue by joining keys with `/`, which is the separator a code already
34
34
  * uses, so an adopter on that host writes the file nested and one handed
35
- * straight to a `ServerMessageRenderer` writes it flat. Both end up here.
35
+ * straight to a `DefaultMessageRenderer` writes it flat. Both end up here.
36
36
  *
37
37
  * `_`-prefixed keys are dropped by PREFIX rather than by matching one literal
38
38
  * name, so a second note added to a file cannot silently become a catalogue