-
Notifications
You must be signed in to change notification settings - Fork 69
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
Ensure we avoid an infinite recursive call stack through any price format filter #8634
Ensure we avoid an infinite recursive call stack through any price format filter #8634
Conversation
Test the buildOption 1. Jetpack Beta
Option 2. Jurassic Ninja - available for logged-in A12s🚀 Launch a JN site with this branch 🚀 ℹ️ Install this Tampermonkey script to get more options. Build info:
Note: the build is updated when a new commit is pushed to this PR. |
Size Change: 0 B Total Size: 1.23 MB ℹ️ View Unchanged
|
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.
Small tweak to the comment, otherwise this looks good and tests well 💯
I'll just go ahead and commit the suggestion and resolve the conversation, and then we can merge!
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.
Looking good! 🚀
…rmat filter (#8634) Co-authored-by: Kristófer Reykjalín <[email protected]>
Changes proposed in this Pull Request
This PR supplements the fix from #8625. Removing only
wc_get_price_decimals
already fixed the issue, but I also removedget_price_thousand_separator
andwoocommerce_price_format
to be extra sure.Testing instructions
Regression Test: Ensure Currency Formatting Still Applied Correctly
fix/infinite-recursive-call-for-price-decimal-separator-filter
branch.Left
-
*
4
Test: Ensure We Avoid An Infinite Recursive Call Through
wc_get_price_decimal_separator
FilterWe were unable to reproduce a second time. So, in order to test this, read through the code to ensure the following stack trace will not be reproducible:
npm run changelog
to add a changelog file, choosepatch
to leave it empty if the change is not significant. You can add multiple changelog files in one PR by running this command a few times.Post merge