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
add feedback question, remove other related. #18262
Conversation
remove feedback links
update screen shot
add feedback question
update close to icon
@peterhashair will take a look at this now. |
@peterhashair The AJAX issue is fixed by this: There are a couple fixes like this in that branch, I can create a quick PR for that specific one. I'm not sure why |
Also, @sgiehl would you have time to checkout this branch and see if you can reproduce the |
@diosmosis sorry, I may be confused you, the command itself works. But the interface looks different from watch. |
@peterhashair oh I see, we're not supporting the use of styles from within Vue right now, instead we're still using the less files and core asset pipeline to define styling. This is mainly to keep the finished asset size down. EDIT: If removing the style from the vue file doesn't change things, let me know. |
remove in line css, change to less file
move translation key to plugin
remove feedback popup
@diosmosis yes it's the line |
…ection # Conflicts: # plugins/Feedback/vue/dist/Feedback.umd.js # plugins/Feedback/vue/dist/Feedback.umd.min.js
update remove some test and feedback related
add draft tests
update feedback add php and UI tests
update test screen shots
add heart to demo page
add feedback back in extend the modal
…ollection # Conflicts: # plugins/CoreHome/vue/dist/CoreHome.umd.min.js
@sgiehl I think this is ready for another review 😀 |
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 another look at the changes. In general most stuff seems to work as expected now 👍
Left a couple of comments. Most of them are actually related to code cleanup and improvements.
Guess afterwards this will be ready to merge
if (location.href.includes('forceFeedbackTest')) { | ||
this.question = 0; | ||
setCookie(cookieName, 0, 7); | ||
} else { |
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.
I guess this one is to ensure the UI test always shows the same question? Guess this could be achieved also by setting the cookie in the UI test using page.setCookie
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.
@sgiehl I tried set page.setCookie in the Test, but its return method was not found. Then I tried to add setCookies
in tests/lib/screenshot-testing/support/page-renderer.js
still no luck
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.
You may need to add setCookie
to the list of proxied methods here: https://github.com/matomo-org/matomo/blob/4.x-dev/tests/lib/screenshot-testing/support/page-renderer.js#L53
If that method is not proxied it will only be available through page.webpage.setCookie
Co-authored-by: Stefan Giehl <stefan@matomo.org>
Co-authored-by: Stefan Giehl <stefan@matomo.org>
Co-authored-by: Stefan Giehl <stefan@matomo.org>
Co-authored-by: Stefan Giehl <stefan@matomo.org>
Co-authored-by: Stefan Giehl <stefan@matomo.org>
update cookie and tests
…ollection # Conflicts: # plugins/CoreHome/vue/dist/CoreHome.umd.js # plugins/CoreHome/vue/dist/CoreHome.umd.min.js
test setcookie in tests
update tests
update tests
update cookie test
extend setCookie in test
update elints format
test set cookie
…atomo into m-18251-feedback-collection
set cookie after goto URL
…atomo into m-18251-feedback-collection
int to string
update set cookie
update test URL
Description:
Fixes:#18251 #18250 #18232
merge @andyjdavis #18277 remove refer us to this branch.
Please ignore the *umd.js file it VUE compile js, when doing a review.
This PR includes:
plugin/feedback/**
plugin/feedback/tests/**
Review