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

[16.0][MIG] website_sale_product_attribute_value_filter_existing: Migration to 16.0 #773

Conversation

anothingguy
Copy link

No description provided.

@anothingguy anothingguy mentioned this pull request Mar 20, 2023
33 tasks
@anothingguy anothingguy marked this pull request as draft March 22, 2023 04:06
@anothingguy anothingguy force-pushed the 16.0-mig-website_sale_product_attribute_value_filter_existing branch from 9c2b71b to d424e0f Compare March 22, 2023 11:16
@anothingguy anothingguy changed the title [16.0][MIG] website_sale_product_attribute_value_filter_existing [16.0][MIG] website_sale_product_attribute_value_filter_existing: Migration to 16.0 Mar 22, 2023
@anothingguy anothingguy force-pushed the 16.0-mig-website_sale_product_attribute_value_filter_existing branch 2 times, most recently from 6957932 to d0966dd Compare March 23, 2023 04:16
@anothingguy anothingguy marked this pull request as ready for review March 23, 2023 04:21
Copy link
Member

@chienandalu chienandalu left a comment

Choose a reason for hiding this comment

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

Tested. Good work, thanks! :) Some minor comments:

Comment on lines 6 to 9
var domReady = new Promise(function (resolve) {
$(resolve);
});
var ready = Promise.all([domReady, session.is_bound]);
Copy link
Member

Choose a reason for hiding this comment

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

I bet this isn't needed :)

Suggested change
var domReady = new Promise(function (resolve) {
$(resolve);
});
var ready = Promise.all([domReady, session.is_bound]);

Copy link
Author

Choose a reason for hiding this comment

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

yep, at the beginning, I didn't add this ready, keep it same as v15. but without this ready, the running tests somehow is not stable, 50% passed and 50% failed. So I searched and tried to add this ready to make sure this tests run when DOM is ready

Copy link
Member

Choose a reason for hiding this comment

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

Yeah, when tours fail that randomly is quite annoying. Ok then 👍

Copy link
Author

Choose a reason for hiding this comment

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

yeah, I removed this redundant code and just keep step_delay to make sure there is enough time between steps

{
test: true,
url: "/shop",
wait_for: ready,
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
wait_for: ready,

url_path="/",
code="%s.run('%s')" % tour,
ready="%s.tours['%s'].ready" % tour,
step_delat=100,
Copy link
Member

Choose a reason for hiding this comment

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

Is it needed anyway?

Suggested change
step_delat=100,
step_delay=100,

Copy link
Author

Choose a reason for hiding this comment

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

yes, I will keep this to make sure there is enough time between steps. Some tests in Odoo modules are still using this

@@ -0,0 +1,3 @@
* Go to Website Shop
* Active product attributes filter
Copy link
Member

Choose a reason for hiding this comment

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

This has changed a bit in v16 as now is a theme panel option that is enabled on either top or bottom in the layout. I'd move it to CONFIGURATION.rst as well.

Copy link
Author

Choose a reason for hiding this comment

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

yes, moved to CONFIGURATION.rst and update more details. thanks for pointing out

@anothingguy anothingguy force-pushed the 16.0-mig-website_sale_product_attribute_value_filter_existing branch from d0966dd to bba2f62 Compare March 24, 2023 10:12
Copy link
Member

@chienandalu chienandalu left a comment

Choose a reason for hiding this comment

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

Thanks! 👍

@OCA-git-bot
Copy link
Contributor

This PR has the approved label and has been created more than 5 days ago. It should therefore be ready to merge by a maintainer (or a PSC member if the concerned addon has no declared maintainer). 🤖

@pedrobaeza
Copy link
Member

/ocabot merge nobump

@OCA-git-bot
Copy link
Contributor

This PR looks fantastic, let's merge it!
Prepared branch 16.0-ocabot-merge-pr-773-by-pedrobaeza-bump-nobump, awaiting test results.

@pedrobaeza
Copy link
Member

/ocabot migration website_sale_product_attribute_value_filter_existing

OCA-git-bot added a commit that referenced this pull request Apr 5, 2023
Signed-off-by pedrobaeza
@OCA-git-bot OCA-git-bot added this to the 16.0 milestone Apr 5, 2023
@OCA-git-bot
Copy link
Contributor

@pedrobaeza your merge command was aborted due to failed check(s), which you can inspect on this commit of 16.0-ocabot-merge-pr-773-by-pedrobaeza-bump-nobump.

After fixing the problem, you can re-issue a merge command. Please refrain from merging manually as it will most probably make the target branch red.

@gurneyalex
Copy link
Member

/ocabot merge nobump

@OCA-git-bot
Copy link
Contributor

What a great day to merge this nice PR. Let's do it!
Prepared branch 16.0-ocabot-merge-pr-773-by-gurneyalex-bump-nobump, awaiting test results.

@OCA-git-bot OCA-git-bot merged commit dcd2e60 into OCA:16.0 Apr 5, 2023
@OCA-git-bot
Copy link
Contributor

Congratulations, your PR was merged at 1718312. Thanks a lot for contributing to OCA. ❤️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.