Conversation
Deploying fliplet-cli with
|
| Latest commit: |
4255acb
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://e571016c.fliplet-cli.pages.dev |
| Branch Preview URL: | https://codex-dev-2075-v3-comms-acti.fliplet-cli.pages.dev |
This branch has not been deployed
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.
Product areas affected
Developer documentation and the V3 API catalog in fliplet-cli.
What does this PR do?
Adds V3-specific guidance to the shared Communicate and Notifications JS and REST references while retaining the V2 examples. Adds V3 catalog pages and a server App Action example that checks the invoking user's session, role, operation, and recipient before sending email. The same authorization boundary is documented for SMS and notifications. Regenerated the documentation indexes and V3 catalog without dropping existing capability search terms.
JIRA ticket
DEV-2075
Result
New V3 documentation directs browser code to invoke a server Action for notification, email, and SMS sends. Existing direct-send endpoints remain functional during migration.
Checklist
Deployment instructions
Deploy these docs before the paired Studio PR is built for production. Studio's prebuild downloads the published V3 catalog and would otherwise replace its updated local snapshot with the old catalog.
Author concerns
A live Builder generation check remains pending: the local headless browser reports an 800×600 screen, so Studio redirects to its desktop-only page. The Jekyll build passed with existing Liquid warnings in unrelated pages. A future V3-wide endpoint block is outside this ticket and must follow migration of existing sends.