Publish APIs #3544
Open
Publish APIs #3544
Conversation
This file contains 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
Closed
Initial publish updates
Regular publish package builder
Regular publishing package submission
* Add Studio API 1 to OAS file #5981 * Update API 1 endpoints missing .json * Fix typo in write-content API in OAS file * [develop] Update examples for write-content API #6798
…publish root becomes publish-all
sumerjabri
reviewed
May 20, 2024
| notifySubmitter: | ||
| type: boolean | ||
| description: notify the submitter when request is approved/rejected | ||
| publishAll: |
There was a problem hiding this comment.
Does this trump the PublishPackageRequest? Feels a bit off. Let's discuss this a bit.
There was a problem hiding this comment.
PublishPackageRequest params are not required. Notice that PublishPackageRequest params are flattened in this request body, it can be as simple as:
{
"siteId": "ed1",
"publishingTarget": "live",
"publishAll": true
}
or contain the list of paths
{
"siteId": "ed1",
"publishingTarget": "live",
"paths": [
{
"path": "/site/website/articles/",
"includeChildren": true,
"includeSoftDeps": true
}
]
}
There was a problem hiding this comment.
I assume combining the two results will make PublishAll win?
There was a problem hiding this comment.
Yes, publish all flag will take precedence
…g when it is not a publish API request (craftercms#3590)
…uplicate insertion on SyncFromRepositoryTask (craftercms#3594)
…f there are other packages affecting the item
…em states update methods
…e other packages affecting the item
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.
craftercms/craftercms#6766
Publish APIs
craftercms/craftercms#6398