-
Notifications
You must be signed in to change notification settings - Fork 6
Implement Endpoint to Edit Post #129
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
Labels
Comments
4 tasks
Fyi we have this endpoint already implemented inside content-publisher. Please take a look at https://github.com/AmplicaLabs/content-publishing-service/blob/main/apps/api/src/api.controller.ts#L88 |
@aramikm you are right. This endpoint is for the Gateway-api service that will proxy the call over to Content-publisher. |
wilwade
referenced
this issue
in ProjectLibertyLabs/gateway
Jul 19, 2024
* Add in redis list of endpoints watching for dsnp graph change * give a descriptive name for clarity
wilwade
referenced
this issue
in ProjectLibertyLabs/gateway
Jul 19, 2024
* Add in redis list of endpoints watching for dsnp graph change * give a descriptive name for clarity
wilwade
referenced
this issue
in ProjectLibertyLabs/gateway
Jul 19, 2024
E2E Testing setup for Content Watcher
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Description
We need to implement a new PUT endpoint to allow to editing content of a specific post. This allows users to update their post without creating a new one,
Acceptance Criteria
/v1/content/{type}/{contentHash}
type
andcontentHash
is required.Technical Specs
Endpoint:
PUT /v1/content/{type}/{contentHash}Authentication:
Required (tokenAuth)Parameters:
Request Body:
Must match the EditPostRequest schema, requiring targetContentHash, targetAnnouncementType, and content.Responses:
Open API Snippet
The text was updated successfully, but these errors were encountered: