@supersoniks/concorde 4.4.2 → 4.5.1

package/docs/src/core/components/ui/tooltip/tooltip.md

@@ -1,82 +0,0 @@
-# Tooltip
-
-<sonic-code>
-  <template>
-    <sonic-tooltip label="Tada : Text appears">hover me</sonic-tooltip>
-  </template>
-</sonic-code>
-
-## Placement
-
-By default, tooltip is centered next to its content
-
-<sonic-code>
-  <template>
-    <sonic-tooltip placement="top" label="Top text">
-      <sonic-button>Top</sonic-button>
-    </sonic-tooltip>
-    <sonic-tooltip placement="bottom" label="Bottom text">
-      <sonic-button>Bottom</sonic-button>
-    </sonic-tooltip>
-     <sonic-tooltip placement="right" label="Right text">
-      <sonic-button>Right</sonic-button>
-    </sonic-tooltip>
-    <sonic-tooltip placement="left" label="Left text">
-      <sonic-button>Left</sonic-button>
-    </sonic-tooltip>
-  </template>
-</sonic-code>
-
-## More placement
-<sonic-code>
-  <template>
-    <div class="flex gap-3 flex-wrap">
-      <sonic-tooltip placement="top-start" label="My tooltip">
-        <sonic-button class="size-40 bg-neutral-200 rounded-lg">Top start</sonic-button>
-      </sonic-tooltip>
-      <sonic-tooltip placement="top-end" label="My tooltip">
-        <sonic-button class="size-40 bg-neutral-200 rounded-lg">Top end</sonic-button>
-      </sonic-tooltip>
-      <sonic-tooltip placement="bottom-start" label="My tooltip">
-        <sonic-button class="size-40 bg-neutral-200 rounded-lg">Bottom start</sonic-button>
-      </sonic-tooltip>
-      <sonic-tooltip placement="bottom-end" label="My tooltip">
-        <sonic-button class="size-40 bg-neutral-200 rounded-lg">Bottom end</sonic-button>
-      </sonic-tooltip>
-      <sonic-tooltip placement="right-start" label="My tooltip">
-        <sonic-button class="size-40 bg-neutral-200 rounded-lg">Right start</sonic-button>
-      </sonic-tooltip>
-      <sonic-tooltip placement="right-end" label="My tooltip">
-        <sonic-button class="size-40 bg-neutral-200 rounded-lg">Right end</sonic-button>
-      </sonic-tooltip>
-      <sonic-tooltip placement="left-start" label="My tooltip">
-        <sonic-button class="size-40 bg-neutral-200 rounded-lg">Left start</sonic-button>
-      </sonic-tooltip>
-      <sonic-tooltip placement="left-end" label="My tooltip">
-        <sonic-button class="size-40 bg-neutral-200 rounded-lg">Left end</sonic-button>
-      </sonic-tooltip>
-    </div>
-  </template>
-</sonic-code>
-
-
-## Focusable
-
-<sonic-code>
-  <template>
-    <sonic-tooltip focusable label="The Concorde made its first transatlantic crossing on September 26, 1973">
-      <sonic-icon library="iconoir" name="chat-bubble-question"></sonic-icon> Focus or hover non interactive element 
-    </sonic-tooltip>
-  </template>
-</sonic-code>
-
-## Disabled
-
-<sonic-code>
-  <template>
-    <sonic-tooltip disabled label="Disabled text">
-      <sonic-button>Tooltip disabled</sonic-button>
-    </sonic-tooltip>
-  </template>
-</sonic-code>
-

package/docs/src/docs/_core-concept/overview.md

@@ -1,57 +0,0 @@
-# lit + tailwind + vite
-
-**Some notes for an overview of Concorde's functioning**
-
-## Standard Web components
-A web component is simply a **custom HTML element** created using web standards:
-
-**web component** = [Custom Elements](https://developer.mozilla.org/en-US/docs/Web/Web_Components/Using_custom_elements) + [shadowDom](https://developer.mozilla.org/fr/docs/Web/Web_Components/Using_shadow_DOM) + [HTML templates](https://developer.mozilla.org/fr/docs/Web/HTML/Element/template)
-
-## Lit Library
-
-Concorde components are written using the lightweight Lit library: https://lit.dev/.
-
-A good portion of the elements documented on the Lit website are standard JavaScript concepts (e.g., [mixins](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes#mix-ins), [tagged template literals](https://developer.mozilla.org/fr/docs/Web/JavaScript/Reference/Template_literals#gabarits_%C3%A9tiquet%C3%A9s)).
-
-The **library simplifies the writing of web components** by automating certain tasks:
-
-- Creation of an **open mode shadow DOM** (the component is accessible from the outside via its shadow root property).
-- [Rendering function](https://lit.dev/docs/components/rendering/) based on [tagged template literals](https://developer.mozilla.org/fr/docs/Web/JavaScript/Reference/Template_literals#gabarits_%C3%A9tiquet%C3%A9s)
-- [Reactive properties](https://lit.dev/docs/components/properties/) that trigger rendering when modified.
-
-Our use of Lit rarely goes beyond this [hello world](https://lit.dev/playground/#sample=examples/hello-world)
-
-## Typescript Language
-
-We write the components in [TypeScript](https://www.typescriptlang.org/docs/handbook/typescript-in-5-minutes.html), which is then compiled into JS.
-
-Static and inferred typing provides stronger validation of the program's functioning during compilation.
-However, we often use the "any" type due to time constraints.
-
-Lit uses TypeScript to simplify development through metadata:
-- Simplified declaration of `custom elements` via @customElement
-- Generation of `reactive properties` via @property.
-
-☢️**Warning**:
-- During development, we operate in interpreted mode, which is faster but allows errors that won't pass during the build.
-- It is important to **build a distribution before pushing the code** to ensure everything is fine.
-
-## Compatibility with Classic JS Libraries
-
-Compatibility issues may arise when using JS libraries, particularly regarding DOM traversal.
-This is because these libraries are blocked from traversing the DOM due to the presence of the shadow DOM.
-Here are some examples of things that may cause problems:
-
-- Latest FontAwesome in SVG mode, icons are not replaced
-- Libraries associated with jQuery
-- document.getElementById
-- ...
-
-## Topics to Explore for Further Learning
-
-
-[🧱 Creating components](#docs/_getting-started/create-a-component.md/create-a-component)
-
-[🎨 Adding styles](#docs/_getting-started/theming.md/theming)
-
-[🥨 Sharing data](#docs/_getting-started/pubsub.md/pubsub)

package/docs/src/docs/_core-concept/subscriber.md

@@ -1,76 +0,0 @@
-# The subscriber mixin
-
-This is a mixin that is commonly extended by Concorde core components and destination components. Pure UI components usually don't extend it, especially those outside of form components.
-
-## DataProvider Attribute: Automatic Filling of Subscriber Properties
-
-Upon being added to the DOM (connectedCallback), subscribers search for the first occurrence of the `dataProvider` attribute in their parent's HTML structure.
-
-The value of this attribute is used to obtain a publisher via the PublisherManager (see [🥨 Sharing Data](#docs/_getting-started/pubsub.md/pubsub)).
-
-The subscriber then subscribes to the publisher as a data template to be filled.
-
-The reactive properties of the component reflect in real-time the properties with the same name in the publisher.
-
-This functionality is commonly used in the generic components [fetch](#core/components/functional/fetch/fetch.md/fetch), [queue](#core/components/functional/queue/queue.md/queue), and [list](#core/components/functional/list/list.md/list).
-
-If the subscriber is inside another subscriber, it can subscribe to a data of its parent using the attribute `subDataProvider = 'address.of.my.data'` instead of the parent's data. This allows for dynamic behavior.
-
-## Automated Translation
-
-In a similar manner, searching for ancestor attributes can be used to configure automatic translation for any property starting with "wording" and ending with a label identifier recognized by the wordingProvider API.
-
-Normally, this API is globally configured and not within the component. Therefore, remember to prefix translatable label identifiers present in the ticketing system, for example, with "wording".
-
-## Reactive Property `props`
-
-The value of this property can be provided as a JSON object or any other value. This value is then assigned to the associated publisher via the `dataProvider` attribute. As a result, the reactive properties of all subscribers associated with the same `dataProvider` are filled as mentioned above.
-
-## Disabling Automatic Filling of Reactive Properties
-
-It is possible to disable the automatic filling of reactive properties in a particular component. To do so, set the variable `noAutoFill = true` in the component's class. However, the reactive property `props` will still be updated.
-
-For example, `sonic-subscriber` and `sonic-fetch` have this attribute because they do not have reactive properties.
-
-**☢ CAUTION:** When creating an object of type Subscriber or Fetcher, make sure to use the mixins and not directly extend the concrete fetch component (`sonic-fetch`) and subscriber component (`sonic-subscriber`). This is because the `noAutofill = true` attribute is set in those components.
-
-**TIPS:** 
-If you disable automatic filling, you will likely make the rendering dynamic by writing expressions like `this.props.my.subproperty`. If `props` is updated, the rendering will be triggered. However, if `this.props.my.subproperty` is directly modified, the rendering will not be triggered. To achieve more reactivity, you can enable rendering when any subproperty is modified. Simply set the variable `renderOnPropsInternalChange = true` in the class that implements the corresponding mixin.
-
-## Data Binding
-
-Suppose that:
-
-- You have a subscriber subscribed to a publisher via its `dataProvider` attribute.
-- The published data has the following structure:
-
-<sonic-code language="javascript">
-  <template>
-    {"img": { "avatar": "my-avatar.jpg", "caption": "look at my smile" }, "email": "an.email@example.com" }
-  </template>
-</sonic-code>
-- We want to keep the display of an image and its `title` attribute up to date, as well as a "contact" button to email the person in the photo. The content of the subscriber could be as follows:
-
-<sonic-code language="html">
-  <template>
-<img data-bind ::src="$img.avatar" ::title="ucFirst|$img.caption" />
-<a data-bind ::href="mailto:$email" ::inner-html="$email"></a>
-  </template>
-</sonic-code>
-
-This example also illustrates:
-
-- Binding to subproperties using dot syntax, as done for the `src` attribute of the `img` tag.
-- Using a simple expression to include the property within a string, as in creating a `mailto` link.
-- Using formatting functions, as in the `title` attribute of the `img` tag. You can find (and add) formatting functions in the `core/utils/Format.ts` file.
-- Writing for properties that are in camel case. Convert everything to lowercase and add hyphens. Note that `innerHTML` (or `outerHTML`) is a special case where no hyphens are added between each letter.
-
-**Note:** Data binding implies that updating the `img.src` data via the publisher will change the photo without any additional calls.
-
-**Special Variables:**
-- `_self_` targets the root of the data. This is useful, for example, when the data is a pure string.
-- `_parent_` targets the parent publisher of the current publisher, if any. For example, the subscribers of lists have the complete data of the list as their parent.
-- `_metadata_` is only used in the case of *sonic-list* at the moment. In a simple list, `_metadata_` see the (list)[] component for further details
-
-**Disabling this functionality:**
-You can disable data binding if it is not needed by calling `DataBinding.disable()`.

package/docs/src/docs/_decorators/ancestor-attribute.md

@@ -1,78 +0,0 @@
-# @ancestorAttribute
-
-The `@ancestorAttribute` decorator automatically injects the value of an ancestor's attribute into a class property at the time of `connectedCallback`.
-
-## Principle
-
-This decorator uses `HTML.getAncestorAttributeValue` to traverse up the DOM tree from the current element and find the first ancestor that has the specified attribute. The value of this attribute is then assigned to the decorated property.
-
-## Usage
-
-### Import
-
-<sonic-code language="typescript">
-  <template>
-import { ancestorAttribute } from "@supersoniks/concorde/decorators";
-  </template>
-</sonic-code>
-
-### Basic example
-
-The component reads `dataProvider` and `testAttribute` from its ancestor wrapper.
-
-<sonic-code language="typescript">
-  <template>
-import { html, LitElement } from "lit";
-import { customElement } from "lit/decorators.js";
-import { ancestorAttribute } from "@supersoniks/concorde/decorators";
-//
-@customElement("demo-ancestor-attribute")
-export class DemoAncestorAttribute extends LitElement {
-  @ancestorAttribute("dataProvider")
-  dataProvider: string | null = null;
-//
-  @ancestorAttribute("testAttribute")
-  testAttribute: string | null = null;
-//
-  render() {
-    return html`
-      <section>
-        <p>dataProvider: <strong>${this.dataProvider || "null"}</strong></p>
-        <p>testAttribute: <strong>${this.testAttribute || "null"}</strong></p>
-      </section>
-    `;
-  }
-}
-  </template>
-</sonic-code>
-
-<sonic-code>
-  <template>
-<div dataProvider="demoDataProvider" testAttribute="test-value-123">
-  <demo-ancestor-attribute></demo-ancestor-attribute>
-</div>
-  </template>
-</sonic-code>
-
-
-## Use cases
-
-This decorator is particularly useful for:
-
-- **Retrieving the `dataProvider`** from an ancestor without having to pass it explicitly
-- **Retrieving the `formDataProvider`** in form components
-- **Retrieving the `wordingProvider`** for translation
-- **Retrieving any other attribute** defined on an ancestor
-
-## Behavior
-
-- The search starts from the current element and traverses up the DOM tree
-- If the attribute is not found, the property will be assigned `null`
-- The injection happens automatically at the time of `connectedCallback`
-- The value is not reactive: it is only updated once when the element is connected to the DOM
-
-## Notes
-
-- This decorator works with any component that has a `connectedCallback` method (such as `LitElement` or components extending `Subscriber`)
-- The search also traverses Shadow DOM if necessary
-- If multiple ancestors have the attribute, the closest one will be used

package/docs/src/docs/_decorators/auto-subscribe.md

@@ -1,199 +0,0 @@
-# @autoSubscribe
-
-The `@autoSubscribe` decorator automatically detects which publishers are accessed within a method and subscribes to them. When any of these publishers change, the method is automatically re-executed.
-
-## Principle
-
-This decorator wraps a method to track which publishers are accessed during its execution. It then subscribes to all accessed publishers, and when any of them change, the method is re-executed. This provides automatic reactivity without manually managing subscriptions.
-
-## Usage
-
-### Import
-
-<sonic-code language="typescript">
-  <template>
-import { autoSubscribe } from "@supersoniks/concorde/decorators";
-  </template>
-</sonic-code>
-
-### Basic example
-
-
-<sonic-code language="typescript">
-<template>
-@customElement("demo-auto-subscribe")
-export class DemoAutoSubscribe extends LitElement {
-  static styles = [tailwind];
-  //
-  @state() displayText: string = "";
-  @state() computedValue: number = 0;
-  //
-  @autoSubscribe()
-  updateDisplay() {
-    const value1 = PublisherManager.get("autoValue1").get() || 0;
-    const value2 = PublisherManager.get("autoValue2").get() || 0;
-    this.computedValue = value1 + value2;
-    this.displayText = `${value1} + ${value2} = ${this.computedValue}`;
-  }
-  //
-  render() {
-    return html`
-      <p><strong>${this.displayText}</strong></p>
-      <div>
-        <sonic-button @click=${() => this.randomizeValue("autoValue1")}>
-          Randomize Value 1
-        </sonic-button>
-        <sonic-button @click=${() => this.randomizeValue("autoValue2")}>
-          Randomize Value 2
-        </sonic-button>
-      </div>
-    `;
-  }
-  //
-  randomizeValue(publisherId: string) {
-    const value = PublisherManager.get(publisherId);
-    value.set(Math.floor(Math.random() * 100));
-  }
-}
-</template>
-</sonic-code>
-
-
-<sonic-code >
-  <template>
-    <demo-auto-subscribe></demo-auto-subscribe>
-  </template>
-</sonic-code>
-
-### Example with render method
-
-<sonic-code language="typescript">
-  <template>
-@customElement("reactive-view")
-export class ReactiveView extends LitElement {
-  @autoSubscribe()
-  render() {
-    const data = PublisherManager.get("myData");
-    const config = PublisherManager.get("config");
-    //
-    // This render method will be automatically re-executed
-    // when myData or config change
-    const value = data.get()?.value || 0;
-    const multiplier = config.get()?.multiplier || 1;
-    //
-    return html`
-      <div>
-        <h1>Result: ${value * multiplier}</h1>
-        <p>Value: ${value}</p>
-        <p>Multiplier: ${multiplier}</p>
-      </div>
-    `;
-  }
-}
-  </template>
-</sonic-code>
-
-## How it works
-
-1. **First execution**: When the method is called, `PublisherManager.collectModifiedPublisher()` is used to track which publishers are accessed
-2. **Subscription**: After execution, the decorator subscribes to all detected publishers
-3. **Re-execution**: When any subscribed publisher changes, the method is automatically called again
-4. **Cleanup**: On `disconnectedCallback`, all subscriptions are automatically removed
-
-## Behavior
-
-- The method is automatically called on `connectedCallback`
-- The method is re-executed whenever any accessed publisher changes
-- Subscriptions are managed automatically (no manual cleanup needed)
-- Only publishers accessed during method execution are subscribed to
-- The decorator uses `queueMicrotask` to batch multiple updates and avoid unnecessary re-renders
-
-## Use cases
-
-This decorator is particularly useful for:
-
-- **Reactive rendering** where the render method depends on multiple publishers
-- **Data transformation** that needs to update when source data changes
-- **Computed properties** that depend on multiple data sources
-- **Automatic synchronization** between publishers and component state
-
-## Complete example
-
-<sonic-code language="typescript">
-  <template>
-import { html, LitElement } from "lit";
-import { customElement } from "lit/decorators.js";
-import { autoSubscribe } from "@supersoniks/concorde/decorators";
-import { PublisherManager } from "@supersoniks/concorde/core/utils/PublisherProxy";
-//
-@customElement("shopping-cart")
-export class ShoppingCart extends LitElement {
-  items: any[] = [];
-  total: number = 0;
-  discount: number = 0;
-  //
-  @autoSubscribe()
-  calculateTotal() {
-    const cart = PublisherManager.get("cart");
-    const promo = PublisherManager.get("promo");
-    //
-    // Access cart items
-    this.items = cart.items.get() || [];
-    //
-    // Access promo code
-    const promoCode = promo.code.get() || "";
-    const discountPercent = promoCode === "SAVE10" ? 0.1 : 0;
-    //
-    // Calculate totals
-    const subtotal = this.items.reduce((sum, item) => 
-      sum + (item.price * item.quantity), 0
-    );
-    this.discount = subtotal * discountPercent;
-    this.total = subtotal - this.discount;
-    //
-    this.requestUpdate();
-  }
-  //
-  connectedCallback() {
-    super.connectedCallback();
-    this.calculateTotal();
-  }
-  //
-  render() {
-    return html`
-      <div class="cart">
-        <h2>Shopping Cart</h2>
-        ${this.items.map(item => html`
-          <div>${item.name} x${item.quantity} - ${item.price}€</div>
-        `)}
-        <div class="total">
-          <p>Subtotal: ${this.total + this.discount}€</p>
-          <p>Discount: -${this.discount}€</p>
-          <p><strong>Total: ${this.total}€</strong></p>
-        </div>
-      </div>
-    `;
-  }
-}
-//
-// When you update the publishers, calculateTotal is automatically called:
-const cart = PublisherManager.get("cart");
-cart.items.set([
-  { name: "Product 1", price: 10, quantity: 2 },
-  { name: "Product 2", price: 15, quantity: 1 }
-]);
-//
-const promo = PublisherManager.get("promo");
-promo.code.set("SAVE10");
-// calculateTotal will be automatically called and the UI will update
-  </template>
-</sonic-code>
-
-## Notes
-
-- This decorator works with any component that has `connectedCallback` and `disconnectedCallback` methods (such as `LitElement` or components extending `Subscriber`)
-- The method is called automatically on `connectedCallback`
-- Remember to call `this.requestUpdate()` if you're updating component properties
-- The decorator uses debouncing via `queueMicrotask` to prevent excessive re-executions
-- For more information about publishers, see the documentation on [Sharing data](#docs/_getting-started/pubsub.md/pubsub)
-

package/docs/src/docs/_decorators/bind.md

@@ -1,164 +0,0 @@
-# @bind
-
-Binds a class property to a path in a publisher. The property updates when publisher data changes.
-
-For Lit re-renders, also add `@state()` on the same property.
-
-**See also:** [@subscribe](#docs/_decorators/subscribe.md/subscribe), [@publish](#docs/_decorators/publish.md/publish), [@get](#docs/_decorators/get.md/get).
-
-## Principle
-
-The decorator subscribes via `PublisherManager` using dot notation. Publisher updates flow into the decorated property.
-
-## Import
-
-<sonic-code language="typescript">
-  <template>
-import { bind } from "@supersoniks/concorde/decorators";
-  </template>
-</sonic-code>
-
-## Example
-
-<sonic-code language="typescript">
-<template>
-@customElement("demo-bind")
-export class DemoBind extends LitElement {
-  static styles = [tailwind];
-  //
-  @bind("demoData.firstName")
-  @state()
-  firstName = "";
-  //
-  @bind("demoData.lastName")
-  @state()
-  lastName: string = "";
-  //
-  @bind("demoData.count")
-  @state()
-  count: number = 0;
-  //
-  render() {
-    return //......
-  }
-  //
-  updateData() {
-    const demoData = PublisherManager.get("demoData");
-    const demoUsers = PublisherManager.get("demoUsers");
-    const randomIndex = Math.floor(Math.random() * demoUsers.get().length);
-    const randomUser = demoUsers.get()[randomIndex];
-    demoData.set({
-      firstName: randomUser.firstName,
-      lastName: randomUser.lastName,
-      count: (demoData.count.get() || 0) + 1,
-    });
-  }
-}
-//
-</template>
-</sonic-code>
-
-<sonic-code>
-  <template>
-    <demo-bind></demo-bind>
-  </template>
-</sonic-code>
-
-## `DataProviderKey` (strict typing)
-
-`@bind` accepts either a string path (legacy) or a `DataProviderKey<T>`. The property type must match `T`. Use `reflect: true` to push local writes back to the publisher (see below). See [DataProviderKey](#docs/_misc/dataProviderKey.md/dataProviderKey).
-
-<sonic-code language="typescript">
-  <template>
-import { bind } from "@supersoniks/concorde/decorators";
-import { DataProviderKey } from "@supersoniks/concorde/dataProviderKey";
-//
-type Data = { count: number };
-const dataKey = new DataProviderKey<Data>("data");
-//
-@bind(dataKey.count, { reflect: true })
-@state()
-count: number = 0;
-  </template>
-</sonic-code>
-
-## Reflect (`reflect: true`)
-
-Two-way sync: reads from the publisher and local assignments call `publisher.set(...)`. An internal guard avoids infinite loops.
-
-<sonic-code language="typescript">
-  <template>
-@bind("userData.profile.avatarUrl", { reflect: true })
-@state()
-avatar: string;
-  </template>
-</sonic-code>
-
-<sonic-code language="typescript">
-  <template>
-@customElement("demo-bind-reflect")
-export class DemoBindReflect extends LitElement {
-  static styles = [tailwind];
-//
-  @bind("bindReflectDemo.count", { reflect: true })
-  @state()
-  withReflect: number = 0;
-//
-  @bind("bindReflectDemo.count")
-  @state()
-  withoutReflect: number = 0;
-//
-  render() {
-    return html`
-      <div class="mb-3">
-        from publisher : ${sub("bindReflectDemo.count") || 0} <br />
-        from component with reflect : ${this.withReflect || 0} <br />
-        from component without reflect : ${this.withoutReflect || 0}
-      </div>
-      <sonic-button @click=${() => this.withReflect++}
-        >Increment with reflect</sonic-button
-      >
-      <sonic-button @click=${() => this.withoutReflect++}
-        >Increment without reflect</sonic-button
-      >
-    `;
-  }
-}
-//
-</template>
-</sonic-code>
-
-<sonic-code toggleCode>
-  <template>
-<demo-bind-reflect></demo-bind-reflect>
-  </template>
-</sonic-code>
-
-## Path syntax
-
-- First segment: data provider id.
-- Nested properties: dot notation.
-- Arrays: numeric index (`items.0`).
-
-### Dynamic paths
-
-Use `${prop}` or `${this.prop}` inside a **normal string literal** (not a JS template literal with backticks). `@bind` re-subscribes when a reactive dependency changes.
-
-> Properties referenced in the pattern must be reactive (`@property`, etc.) or you must call `requestUpdate` manually.
-
-<sonic-code>
-  <template>
-    <demo-bind-dynamic></demo-bind-dynamic>
-  </template>
-</sonic-code>
-
-## Behavior
-
-- Subscribes at `connectedCallback`, unsubscribes at `disconnectedCallback`.
-- If the path does not exist yet, a publisher may be created with `null`.
-
-## Notes
-
-Works with any component that has the usual DOM lifecycle (`LitElement`, `Subscriber` mixin, etc.).
-
-Shared data: [Sharing data](#docs/_getting-started/pubsub.md/pubsub).