@instructure/platform-modules 0.2.0 → 0.3.0

package/dist/types/domain.d.ts

@@ -1,7 +1,7 @@
 import { z } from 'zod';
 import { CompletionRequirementTypeSchema, ModuleItemStatusSchema, ModuleItemTypeSchema, ModuleStatusSchema } from './enums';
 /**
- * The normalised domain model shared by every host and every transport.
+ * The normalized domain model shared by every host and every transport.
  *
  * This is deliberately smaller than what either Canvas LMS or Canvas Career
  * fetches today: it is the *intersection* of what both need to render a
@@ -9,7 +9,7 @@ import { CompletionRequirementTypeSchema, ModuleItemStatusSchema, ModuleItemType
  * assignment overrides) rides in `extensions` rather than widening the model,
  * so a host can never make the shared contract depend on its own UI.
  *
- * Three normalisation rules hold at every adapter boundary:
+ * Three normalization rules hold at every adapter boundary:
  *
  *   1. Ids are strings. GraphQL hands back `_id`/`id`, REST hands back numbers.
  *   2. `published` is always populated. REST omits the field for students,
@@ -133,7 +133,7 @@ export interface Module {
     progress?: ModuleProgress;
     extensions?: Record<string, unknown>;
 }
-/** Relay-style cursor pagination, normalised across GraphQL and REST. */
+/** Relay-style cursor pagination, normalized across GraphQL and REST. */
 export interface PageInfo {
     hasNextPage: boolean;
     endCursor: string | null;

package/dist/types/enums.d.ts

@@ -4,7 +4,7 @@ import { z } from 'zod';
  *
  * The types in `domain.ts` are `z.infer`red from these rather than hand-written
  * beside them. That inversion is the point, and it fixes a trap: when the union
- * and the `z.enum` were two separate lists, the two ways of desynchronising them
+ * and the `z.enum` were two separate lists, the two ways of desynchronizing them
  * behaved differently.
  *
  *   - Add a member to the `z.enum` but not the union → compile error. Loud.
@@ -78,7 +78,7 @@ export declare const ModuleStatusSchema: z.ZodEnum<[
  *
  * `unknown` is the forward-compatibility member: a seventh type shipping in
  * Canvas must not make this package fail to parse a module. It lands here, the
- * label humanises it, and nothing downstream has to handle a string it has never
+ * label humanizes it, and nothing downstream has to handle a string it has never
  * heard of.
  */
 export declare const CompletionRequirementTypeSchema: z.ZodEnum<[

package/dist/types/navigation.d.ts

@@ -2,7 +2,7 @@ import { MouseEvent } from 'react';
 import { ModuleItem } from './domain';
 /**
  * Optional host navigation for item rows. Titles link to `ModuleItem.url`
- * without it. Pass a stable reference: `ModuleItemRow` is memoised.
+ * without it. Pass a stable reference: `ModuleItemRow` is memoized.
  */
 export interface ModuleItemNavigation {
     /** Rewrite an item's href. Falls back to `item.url` when it returns nullish. */

package/dist/types/schemas.d.ts

@@ -4,7 +4,7 @@ export { CompletionRequirementTypeSchema, ModuleItemStatusSchema, ModuleItemType
 /**
  * Runtime schemas for the domain model.
  *
- * These validate at the *adapter boundary*, after normalisation — not at the
+ * These validate at the *adapter boundary*, after normalization — not at the
  * wire. That is deliberate: the wire shapes differ per transport, but every
  * adapter must produce something that satisfies these, which is what makes
  * "one contract, two backends" enforceable rather than aspirational.

package/locales/en.json

@@ -26,7 +26,6 @@
   },
 
   "filterGroupLabel": "Filter",
-  "filterChipWithCount": "%{label} (%{count})",
   "filterAll": "All",
   "filterInProgress": "In progress",
   "filterComplete": "Complete",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@instructure/platform-modules",
-  "version": "0.2.0",
+  "version": "0.3.0",
   "type": "module",
   "main": "./dist/index.js",
   "module": "./dist/index.js",