EZP-27762 content/edit routing conflict with legacy #143
Conversation
Spiked route+form to create a draft of an existing content
Given that a content with id N exists
When I go to /content/create/draft/N
Then I see a content draft creation form with the following fields:
|name|
|contentId|
|fromVersionNo|
|fromLanguage|
|toLanguage|
When I submit the form
Then a draft of the content with id N is created
(cherry picked from commit 3ab2ce0)
Spiked content edition
Given a content with id N with a draft number 2 that I can edit
When I go to /content/edit/N/2
Then I see a content edit form
When I click on the publish button
Then the draft is published
(cherry picked from commit a6506e2)
There was a problem hiding this comment.
I'm ok with this, however there might be alternative routes as well to avoid the conflict. So very much interested in hearing what @bdunogier and @yannickroger thinks about this.
|
NOTE: One alternative here is to pick a different verb then |
Not bad. But the downside is that this resource doesn't only update, it also publishes (if you ask it to). |
|
Also, do we care about the BC break (route change) ? |
Which bc break? This was reverted from stable branch before 1.11 release, so it's only in master. |
Ensure our route doesn't conflict with legacy content edit, by changing
/content/edit/...to/content/edit/draft/....Debatable: Renaming the route from
ez_content_edittoez_content_draft_edit, as I've done. The fix is smaller if we don't.