Expose Collection guestbookRoot setting through API - #12611
Expose Collection guestbookRoot setting through API#12611stevenwinship wants to merge 8 commits into
Conversation
This comment has been minimized.
This comment has been minimized.
1 similar comment
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
1 similar comment
This comment has been minimized.
This comment has been minimized.
92713c8 to
b707c45
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
2 similar comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Review follow-up summaryReviewed this PR and worked through the follow-ups for @stevenwinship — everything's now resolved:
All CI checks are now green, including the SonarCloud quality gate, and both review threads are marked resolved. The only thing outstanding for merge is an approving review — this PR currently has no approvals (my review was comment-only) and no reviewers requested. |
| "datasetFileCountLimit": 10, | ||
| "guestbookRoot": false |
There was a problem hiding this comment.
These should be documented in doc/sphinx-guides/source/api/native-api.rst
There was a problem hiding this comment.
added documentation
Covers POST /api/dataverses defaulting guestbookRoot to false when omitted, and setting it to true when included in the request body. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Covers the new guestbookRoot branches in JsonParser.parseDataverse, JsonParser.parseDataverseDTO, and JsonPrinter.json(Dataverse) with unit-test assertions, to close the SonarCloud new-code coverage gap left by the IT-only test. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
- JsonParserTest: cover the containsKey("guestbookRoot") false branch
in parseDataverseDTO, which was previously only exercised with the
key present.
- UpdateDataverseCommandTest: new unit test covering both branches of
updateDataverseFromDTO's guestbookRoot handling (set vs. left
unchanged), previously only covered indirectly by an IT test.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
190639d to
d1e87c6
Compare
This comment has been minimized.
This comment has been minimized.
|
|
📦 Pushed preview images as 🚢 See on GHCR. Use by referencing with full name as printed above, mind the registry name. |



What this PR does / why we need it: SPA needs the ability to view and modify the "guestbookRoot" setting of a Collection
Which issue(s) this PR closes:#12459
Special notes for your reviewer:
Suggestions on how to test this:See DatasetsIT. Make call to create/update dataverse and verify the setting.
Does this PR introduce a user interface change? If mockups are available, please link/include them here:
Is there a release notes update needed for this change?:included
Additional documentation: