feat: translation flows, revision conflicts, delete scopes, article moves and a target site for new articles
This commit is contained in:
1 parent
339e646eb8
commit
45fbbc33b1
93 files changed
+7630
-294
No files matched your search
@@ -107,18 +107,16 @@ Feature: Sites and authors in the Editor, Articles and Profile screens
|
||||
And the helper text reads "Canonical host: journal.renew.example"
|
||||
And the select is available to every role that can edit the article
|
||||
|
||||
Scenario: Site select options
|
||||
When the user opens the Site select
|
||||
Then each option shows the site name and its host, and the default site is first
|
||||
Scenario: Site field
|
||||
When the user activates the Site field
|
||||
Then the Move article panel opens with the sites in the order of GET /v1/site/ and the current site marked
|
||||
|
||||
Scenario: Changing the site is an edit
|
||||
Scenario: Choosing a site no longer stages an edit (superseded by localization_translation_flows)
|
||||
Given the editor shows "Saved" and the article is on "Renew"
|
||||
When the user chooses "Journal"
|
||||
Then the status becomes "Unsaved changes" and Save is enabled
|
||||
And no request is sent yet
|
||||
When the user activates Save
|
||||
Then exactly one PATCH /v1/article/12 is sent containing site_id 2
|
||||
And on 200 the status is "Saved" and the helper text shows the new host
|
||||
When the user activates the Site field
|
||||
Then the Move article panel of localization_translation_flows opens, with the sites listed
|
||||
And choosing a site there does not change the status, does not enable Save and sends no site_id
|
||||
And moving the article is the only way to change its site, through POST /v1/story/{story_id}/move
|
||||
|
||||
Rule: Author list
|
||||
|
||||
|
||||
Reference in new issue
Block a user