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
[Vue] migrate piwik-reporting-menu directive to vue #18423
Conversation
* use jQuery click for expand on click * undo submodule change
…field appearing in a select option list, but only at first
Tests should be passing for this one. Fixed a bunch of smaller bugs towards the end. |
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.
Left a couple of comments for stuff I found while looking through the code & test changes. Did not yet complete the manual testing. will add further comments if I find anything else...
oldValue: null, | ||
modifiers: {}, | ||
dir: {}, |
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.
Just out of curiosity: Are those attributes needed for anything? Can't see that they are used anywhere 🤔
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.
These are required by the DirectiveBinding
interface in Vue. If you remove them, phpstorm should complain. Typescript will also complain, but possibly not when calling vue:build. For the adapter we're passing a fake object just to trigger the directive logic correctly.
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.
Had a quick look at the UI file changes. Seems one css change needs to be reverted. And on the PrivacyManager tests it looks like that before the All Websites
entry was preselected in the site selector. Now that switched to a specific site. Would it be easy to change that? Otherwise we could also define that as expected behavior and add according attributes to the site selector on the privacy settings pages, so that all websites
is preselected
Oh, I thought it didn't have an initial site set, but it is initialized in the controller. Looked into a bit, this is a different issue, though I'm not sure what... Setting data on the vue app isn't working, it doesn't propagate to the root component in the app. Will see if I can figure it out. |
@sgiehl fixed it w/ an extra nextTick(). Not sure why this works, but it seems to. |
db916f2
to
6fc6337
Compare
@diosmosis there still seem to be some changes in the UI files that look unexpected. The usermanagers results changed, but imho they shouldn't have |
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.
working as expected, I think the test is being fixed.
@sgiehl: @peterhashair was faster by a couple minutes, but it looks like the change was a fix to some broken behavior, the first failure is for |
@diosmosis I guess some ui changes might still be some sort of incorrect: |
This works for me locally (when using tests/PHPUnit/proxy). It might be a race condition. The menu is updated, that's something I specifically had to fix (specifically due to a race condition w/ the jquery dashboard code not waiting for dashboard load to finish) though it might be possible the fix is in a different PR. I'll look a bit more to see if I can reproduce it. |
Description:
Changes:
window.widgetsHelper
typings to index.d.ts.Review