Skip to content
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

EZP-30187: As an editor I would like content tree to always have expanded current location #149

Conversation

tischsoic
Copy link
Contributor

@tischsoic tischsoic commented Feb 28, 2019

JIRA: https://jira.ez.no/browse/EZP-30187

Requires backend part

Screenshot

mkiru8tkap

nextSubtree = {
'_media-type': 'application/vnd.ez.api.ContentTreeLoadSubtreeRequestNode',
locationId: locationId,
limit: 1,
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This probably will have to be resolved by backend because in the frontend I don't know at what position is e.g. currentLocation which I have to expand automatically.

Because of this this PR is WIP now.

nextSubtree = {
'_media-type': 'application/vnd.ez.api.ContentTreeLoadSubtreeRequestNode',
locationId: locationId,
limit: this.props.subitemsLoadLimit,
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note: later it would be changed to something else.

@tischsoic tischsoic changed the title [WIP] EZP-30187: As an editor I would like content tree to always have expanded current location EZP-30187: As an editor I would like content tree to always have expanded current location Mar 1, 2019
@tischsoic
Copy link
Contributor Author

ping @dew326 - ready for review

@lserwatka lserwatka merged commit 012e4ba into master Mar 1, 2019
@lserwatka lserwatka deleted the EZP-30187-always-have-current-location-expanded-in-content-tree branch March 1, 2019 11:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

3 participants