Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for signed/published-resource contents in files #640

Merged
merged 5 commits into from
Apr 18, 2024

Conversation

piemonkey
Copy link
Contributor

Overview

Handle the possibility that published or signed resources have content in a file instead of directly in the resource as a string. Also added some very basic error handling for file lookups instead of just returning blank data.

connected issues and PRs:

Part of #639
Needed for lblod/app-gelinkt-notuleren#181

Setup

Needs to be tested with the app-gn from the PR.

How to test/reproduce

See the app-gn PR on how to test/reproduce.

Challenges/uncertainties

The sheer number of deprecations makes it hard to see messages...

Checks PR readiness

  • UI: works on smaller screen sizes
  • UI: feedback for any loading/error states
  • Check cancel/go-back flows
  • Check database state correct when deleting/updating (especially regarding relationships)
  • changelog
  • npm lint
  • no new deprecations

Setting 'body' on a versioned-notulen doesn't have any meaning, and
presumably is a relic of an older model. behandelingen-list had a
controller that was supplying a value used elsewhere in the parent, so I
made it an argument.
@piemonkey piemonkey merged commit be06dbf into master Apr 18, 2024
3 checks passed
@piemonkey piemonkey deleted the fix/signed-resource-files branch April 18, 2024 07:19
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.

3 participants