feat(support): add private report conversations - #4
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Context
Follow-up to #1.
This provides the service contract needed for Nextcloud Native to show support status changes and maintainer questions inside the app. Capability access remains scoped to the existing private report link; maintainer writes require the authenticated admin session and CSRF token. Message bodies are bounded to 8 KiB and encrypted with report/message-specific associated data.
Validation
On the dedicated build host at commit
76c6f78db32baa0062df4fa85bc3150d44d15920:npm ci,npm run lint,npm test,npm run build(7 tests passed)go test ./...,go vet ./...The migration uses an
ON DELETE CASCADEreport relationship; in-memory retention tests and storage behavior remove message data with the report.