Skip to content

feat(updates): add Update publishing form - #944

Merged
danieltruong merged 2 commits into
developfrom
feat-updates-form
Sep 23, 2026
Merged

danieltruong merged 2 commits into
developfrom
feat-updates-form

Conversation

@danieltruong

Copy link
Copy Markdown
Collaborator

Adds the Update publishing form (PUBLIC-159, PUBLIC-160).

What changes:

  • Staff can set category, short headline, summary, featured image with alt text, attachments, regions, location, engagement link and subject.
  • An Update is saved as draft, published, or scheduled with a future publish date.
  • Delete becomes archive.
  • Edits send dateUpdated. If someone else saved first, the API returns 409 and the form says so.
  • Changing the project or switching to the comment period type clears documents picked from the old project.
  • Unused delete and pin code removed from the activity detail and pins rows.

Needs eagle-api from its matching PR deployed first.

Not yet checked in a browser, because the local form sits behind the Keycloak login. Please try it on dev before merge.

Staff can set category, short headline, summary, featured image,
attachments, regions, location, engagement link and subject, and save
an Update as draft, published or scheduled.

- delete becomes archive
- edits send dateUpdated; a 409 shows a stale-edit message
- pin toggle keeps the returned dateUpdated so the next save works
- drop unused delete and pin code from activity-detail-table-rows

Refs: PUBLIC-159, PUBLIC-160
Switching an Update to the comment period type reset the project but
kept the featured image and attachments picked from it. The type change
now runs the same clearing path as a project change.

Move the 409 spec to the pin toggle staff can reach and drop the unused
togglePin from pins-table-rows.
@danieltruong
danieltruong merged commit 195674a into develop Sep 23, 2026
4 checks passed
@danieltruong
danieltruong deleted the feat-updates-form branch September 23, 2026 20:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant