feat(customersupport): document the API with development Swagger UI - #18
Merged
Conversation
github-actions
Bot
added
documentation
amasen02
marked this pull request as ready for review
September 12, 2026 22:35
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
1 participant
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.
Fixes #4.
Customer Support now serves a self-hosted Swagger UI at /swagger in Development, using the existing ASP.NET Core OpenAPI document. Carter/Minimal API summaries and typed response metadata document the three support operations; tests resolve schema references and verify session/message properties and pagination envelopes. Production exposes neither the UI nor the document.
The API's strict CSP and authorization remain intact. Development Swagger routes permit self-hosted assets and one exact SHA-256 hash for the bundled logo's inline SVG style; external validation is disabled. Setup guides use HTTPS and accurately describe the embedded dashboard/support-console routes.
Validation at 2ff5e13: all9 hosted checks pass;59 CustomerSupport tests pass with zero skipped; Chromium, Firefox and WebKit each execute both customer journeys against the merged HTTPS frontend40ed245. CI captures actual documentation responses and headers. Browser-harness rendering shows all3 operations/all14 expected model properties, no CSP/runtime errors, and only same-origin200 resources. All8 final captured body hashes and CSP headers match the browser-verified fixture. Windows Application Control blocks local assembly execution; Linux CI provides the full-suite proof.