-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Tax price fields have wrong naming convention #2918
Comments
We'll take care of that by the refactoring efforts. We'll apply the following changes:
We'll keep the older property names as depreciated for some time (would be awesome to add the eslint rule for checking the property names) |
…price` being used for catalog rules (#3099)
Will be closed with #3156 |
@pkarw I checked changes on Bugfix/2918 branch |
Hi! Thanks for testing this out! @alinadivante this is intended behavior, there is a |
Thanks @pkarw ! Please include information such as test instructions next time, if there is something what we need to change in config or something like that - let us know! :) |
Current behavior
Some object attributes don't respect the naming convention used by all others (underscore, not camelCase)
They are:
Expected behavior
Respect naming convention used by all others, eg price_incl_tax
Steps to reproduce the issue
Open network inspector
Visit
https://demo.vuestorefront.io/gear/gear-3/joust-duffle-bag-1.html
See response in
https://demo.storefrontcloud.io/api/catalog/vue_storefront_catalog/product/_search?_source_exclude=%2A.msrp_display_actual_price_type%2Crequired_options%2Cupdated_at%2Ccreated_at%2Cattribute_set_id%2Coptions_container%2Cmsrp_display_actual_price_type%2Chas_options%2Cstock.manage_stock%2Cstock.use_config_min_qty%2Cstock.use_config_notify_stock_qty%2Cstock.stock_id%2Cstock.use_config_backorders%2Cstock.use_config_enable_qty_inc%2Cstock.enable_qty_increments%2Cstock.use_config_manage_stock%2Cstock.use_config_min_sale_qty%2Cstock.notify_stock_qty%2Cstock.use_config_max_sale_qty%2Cstock.use_config_max_sale_qty%2Cstock.qty_increments%2Csmall_image%2Csgn%2C%2A.sgn&from=0&request=%7B%22query%22%3A%7B%22bool%22%3A%7B%22filter%22%3A%7B%22bool%22%3A%7B%22must%22%3A%5B%7B%22terms%22%3A%7B%22category_ids%22%3A%5B4%2C3%5D%7D%7D%2C%7B%22terms%22%3A%7B%22visibility%22%3A%5B2%2C3%2C4%5D%7D%7D%2C%7B%22terms%22%3A%7B%22status%22%3A%5B0%2C1%2C2%5D%7D%7D%5D%7D%7D%7D%7D%7D&size=8&sort=
Repository
Can you handle fixing this bug by yourself?
Which Release Cycle state this refers to? Info for developer.
Pick one option.
develop
branch and create Pull Request2. Feature / Improvement
back todevelop
.release
branch and create Pull Request3. Stabilisation fix
back torelease
.hotfix
ormaster
branch and create Pull Request4. Hotfix
back tohotfix
.The text was updated successfully, but these errors were encountered: