-
Notifications
You must be signed in to change notification settings - Fork 1
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
QA-15066: add unpublish action on vanity urls #221
Conversation
@@ -37,13 +37,12 @@ export const Toolbar = ({selection, onChangeSelection, actions}) => { | |||
actions={actions} | |||
render={ButtonRenderer} | |||
filter={action => { | |||
return action.key !== 'updateVanity'; | |||
return !['updateVanity', 'unpublish'].includes(action.key); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks dirty to filter action here, since actions are normally based on targets to choose where they should appears or not. But it was already like that before your changes, so I am assuming we can keep this for now.
}; | ||
|
||
export const atLeastOneLockedForValidation = urls => { | ||
return urls.some(url => url.default.lockedAndCannotBeEdited && url.default.lockInfo.details.some(detail => detail.type === 'validation')); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we have undefined
protection on this nesting object access ?
The merge-base changed after approval.
* QA-15066: add unpublish action on vanity urls * fix publication check failing after moving a url
https://jira.jahia.org/browse/QA-15066