Release v1.121.0 - staging → master

docs/development-guide/15-api-events.md

@@ -0,0 +1,73 @@
+# API Events
+
+In order to display Events, Cloud Manager polls the [account/events](https://www.linode.com/docs/api/account/#events-list) endpoint at a 16 second interval, or every 2 seconds if there are “in-progress” events.
+
+In order to display these messages in the application (Notification Center, /events page), we compose messages according to the Event key (`EventAction`). Each key requires an entry and set of custom messages for each status (`EventStatus`), dictated by API specs. Not every Status is required for a given Action.
+
+## Adding a new Action and Composing Messages
+
+In order to add a new Action, one must add a new key to the read-only `EventActionKeys` constant array in the api-v4 package.
+Once that's done, a related entry must be added to the `eventMessages` Event Map. In order to do so, the entry can either be added to an existing Event Factory or a new one. `eventMessages` is strictly typed, so the decision where to add the new Action will be clear. ex:
+
+```Typescript
+import { EventLink } from '../EventLink';
+
+import type { PartialEventMap } from '../types';
+
+export const linode: PartialEventMap<'linode'> = {
+  linode_addip: {
+    notification: (e) => (
+      <>
+        An IP address has been <strong>added</strong> to Linode{' '}
+        <EventLink event={e} to="entity" />.
+      </>
+    ),
+  },
+};
+```
+
+The convention to compose the message is as follows:
+- Use the `<EventLink />` component for linking `entity` or `secondary_entity`. This component includes a lookup util to format the link `href` according to the feature.
+- The bolding should only be applied to:
+  - the primary action: (ex: `<strong>created</strong>`) 
+  - its correlated negation for negative actions (ex: `could <strong>not</strong> be <strong>created</strong>.`)
+- The `message` should be also handled via the `<EventMessage message={e.message} />` in order to handle potential formatting from the API string (ticks to indicate code blocks).
+
+## Displaying Events in snackbars
+
+We can leverage the Event Message factories in order to display events in snackbars/toasts when a given action gets triggered via APIv4.
+
+```Typescript
+const { enqueueSnackbar } = useSnackbar();
+
+try {
+  const successMessage = getEventMessage({
+    action: 'image_upload',
+    entity: {
+      label: 'Entity',
+      url: '/image/123',
+    },
+    status: 'notification',
+  });
+
+  const showToast = (variant: any) =>
+  enqueueSnackbar(successMessage, {
+    'success',
+  });
+}, catch {
+  const failureMessage = getEventMessage({
+    action: 'image_upload',
+    // in this case we don't add an entity since we know we can't link to it
+    status: 'failed',
+  });
+
+  const showToast = (variant: any) =>
+  enqueueSnackbar(failureMessage, {
+    'error',
+  });
+}
+```
+
+Both `action` and `status` are required. The `entity` and `secondary_entity` can optionally be passed to allow for linking. **Note**: it is possible the Event Message linking will be missing if the action status message expects either value but isn't not provided by the instance call.
+
+If a corresponding status does not exist (ex: "failed"), it's encouraged to add it to the Action. Event if not triggered by the API, it can be useful to have a reusable Event Message to use through the App.

packages/api-v4/CHANGELOG.md

@@ -1,3 +1,22 @@
+## [2024-06-10] - v0.119.0
+
+
+### Added:
+
+- `tags` field in `Image` type ([#10466](https://github.com/linode/manager/pull/10466))
+- New endpoint for `object-storage/types` ([#10468](https://github.com/linode/manager/pull/10468))
+- `members` to `DatabaseInstance` and `Database` types ([#10503](https://github.com/linode/manager/pull/10503))
+- New event `tax_id_invalid` for account tax id ([#10512](https://github.com/linode/manager/pull/10512))
+
+### Changed:
+
+- Update return type of `updateDatabase` to be `Database` ([#10503](https://github.com/linode/manager/pull/10503))
+- Add lke_cluster_id to Linode interface ([#10537](https://github.com/linode/manager/pull/10537))
+
+### Upcoming Features:
+
+- Update images endpoints to reflect the image service API spec ([#10541](https://github.com/linode/manager/pull/10541))
+
 ## [2024-05-28] - v0.118.0
 
 

packages/api-v4/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@linode/api-v4",
-  "version": "0.118.0",
+  "version": "0.119.0",
   "homepage": "https://github.com/linode/manager/tree/develop/packages/api-v4",
   "bugs": {
     "url": "https://github.com/linode/manager/issues"
@@ -67,7 +67,7 @@
     "lint-staged": "^13.2.2",
     "prettier": "~2.2.1",
     "tsup": "^7.2.0",
-    "vitest": "^1.0.1"
+    "vitest": "^1.3.1"
   },
   "lint-staged": {
     "*.{ts,tsx,js}": [