-
-
Notifications
You must be signed in to change notification settings - Fork 221
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
TASK: Cleanup of internal VIE usage in JS backend #188
Conversation
Hey Aske, I just read over the change, and I really like what I have seen. So from my side, this is a 👍 by reading, although I think this change needs some more intense testing. All the best, |
@kdambekalns it's not important for the release, so will probably rebase after feature freeze |
and it's basically just stuff I found while fixing #186 |
👍 |
Looks good and seems to work fine. Just played with it a bit. 👍 but conflicts need to be solved before merging. |
rebased |
👍 fixed StyleCI issue (unrelated to change) |
👍 rebased |
When a new page is loaded the node type and node type label wasn't updated for the page root node in the context structure tree.
Adds a getter method for retrieving a previous attribute from the VIE entity instead of accessing VIE directly or getting all attributes just to get one.
Removes usage of the VIE entity in the trees used by the listernes, instead the node entity is used.
Adds a getter method for checking if a attribute exists in the VIE entity instead of accessing VIE directly or getting all attributes to check.
included all of the changes in #416 instead |
This change removes a lot of the direct interaction with VIE and replaces it with the node model.
Additionally the VIE namespace is no longer used outside VIE so the configuration is removed.