You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 6e5a843
Browse filesBrowse the repository at this point in the historyBrowse files
Aligns configuration vocabulary that differed between products; the product is pre-1.0. Every renamed key has a `config.removed-key` entry naming its replacement, a CFG-NAME-5 row, a `BREAKING:` line in the product CHANGELOG, a note in `release/notes/config-conventions/`, and updated examples, fixtures, docs and regenerated schemas. No migration code.
BREAKING:
- Casework, Documents and Messaging access profiles: `role` is renamed `actsAs`; values unchanged. The schema definitions `CaseworkRole` and `AccessRole` become `CaseworkActsAs` and `ActsAs`, and the Casework diagnostic `casework.access-profile.missing-role` becomes `casework.access-profile.missing-acts-as`. BReg profiles and the data sense of `role` (event records, Evidence subjects) are unchanged.
- Coordinator: `title` is renamed `label` on a project, function, operation and step; the explain member `presentation.title` becomes `presentation.label`; the duplicate-title diagnostics become `...duplicate-function-label`, `...duplicate-operation-label` and `...duplicate-step-label`.
- Casework holiday-set file: `holidaySet` is renamed `id`, and an optional `label` is allowed. A calendar's `holidaySet` member, which names the set it uses, is unchanged.
- Scheduling: a holiday set's `because` is renamed `label`, and `label` is now optional (the id names a set that writes none), as in the Casework holiday-set file. The schema definition `HolidaySetPolicy` becomes `HolidaySet`. `because` stays on every other Scheduling item.
- `caseworkctl dev` report: a client names `actsAs` where it named `role`.
- Upgrade: this release does not read state stored by 0.45.0 or earlier. Start Casework and Scheduling on a new database; finish Coordinator runs before upgrading. A stored document that holds a removed member is refused with a message that says it was stored by an earlier release and names the member.
Additive:
- Coordinator event triggers accept an optional `label` and `description`, stored under `presentation.eventTriggers.<id>`, reported by `check --explain`, and outside the semantic revision (a wording edit keeps `workflowRevision`). Closes#2549.
- Casework, Documents, Messaging and Evidence access profiles accept an optional `label` and `description` (BReg profiles already have `display`). They are accepted for authoring and tooling. Casework keeps them in the review policy description, which any caller who may read that description, requesters included, can see, and they do not change a policy's behavioral binding. Evidence drops them at compile; Documents and Messaging only parse them, and none serve them until a view exists.
Signed-off-by: Jeremi Joslin <jeremi@joslin.fr>
replacement:"Write accessProfiles as a mapping from each id to the rest of its entry, accessProfiles: {PROFILE_ID: {role: ...}}, with no id member. See row F4 of the format table in the Casework CHANGELOG.",
319
+
replacement:"Write accessProfiles as a mapping from each id to the rest of its entry, accessProfiles: {PROFILE_ID: {actsAs: ...}}, with no id member. See row F4 of the format table in the Casework CHANGELOG.",
/// A name for the profile, accepted for authoring and tooling; never matched against a caller. Part of the review policy description, which any caller who may read that description can see.
/// What the profile is for, accepted for authoring and tooling; never matched against a caller. Part of the review policy description, which any caller who may read that description can see.
0 commit comments