This PR was merged into the 1.13 branch.
Discussion
----------
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.13 <!-- see the comment below --> |
| Bug fix? | no |
| New feature? | no |
| BC breaks? | no |
| License | MIT |
<!--
- Bug fixes must be submitted against the 1.12 branch
- Features and deprecations must be submitted against the 1.13 branch
- Make sure that the correct base branch is set
To be sure you are not breaking any Backward Compatibilities, check the documentation:
https://docs.sylius.com/en/latest/book/organization/backward-compatibility-promise.html
-->
Commits
-------
3c6002b63f Cover Seeing payment method instructions behat scenario
This PR was merged into the 1.13 branch.
Discussion
----------
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.13 <!-- see the comment below --> |
| Bug fix? | no |
| New feature? | no |
| BC breaks? | no |
| License | MIT |
<!--
- Bug fixes must be submitted against the 1.12 branch
- Features and deprecations must be submitted against the 1.13 branch
- Make sure that the correct base branch is set
To be sure you are not breaking any Backward Compatibilities, check the documentation:
https://docs.sylius.com/en/latest/book/organization/backward-compatibility-promise.html
-->
Commits
-------
200b4409f5 Add @no-api tag to preventing to pay for cancelled order scenario
This PR was merged into the 1.12 branch.
Discussion
----------
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.12 |
| Bug fix? | yes |
| New feature? | no? |
| BC breaks? | no |
| Deprecations? | no |
| Related tickets | fixes#14131 |
| License | MIT |
Inb4 someone asks why there's no API coverage or `no-api` tags:
- sorting is possible via API so `no-api` does not apply
- coupons have no crud in API ATM
- catalog promotions have no sorting specified in API
The 2 last points would be doable in this PR, but then it would have to go to 1.13 since new features would be introduced, and I see no point in blocking the bugfix part alone for 1.12.
Commits
-------
9cefb206b0 [Admin] Fix inability of sorting promotion coupons and catalog promotions
6d170e5127 [UI][Behat] Sorting promotion coupons
8564ed5431 [UI][Behat] Sorting catalog promotions
e88b0f4eaa [Behat][Postgres][Promotion] Disable sorting scenarios for nullable fields
This PR was merged into the 1.13 branch.
Discussion
----------
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.13 <!-- see the comment below --> |
| Bug fix? | no |
| New feature? | no |
| BC breaks? | no |
| Deprecations? | no <!-- don't forget to update the UPGRADE-*.md file --> |
| License | MIT |
<!--
- Bug fixes must be submitted against the 1.12 branch
- Features and deprecations must be submitted against the 1.13 branch
- Make sure that the correct base branch is set
To be sure you are not breaking any Backward Compatibilities, check the documentation:
https://docs.sylius.com/en/latest/book/organization/backward-compatibility-promise.html
-->
Commits
-------
e37791f5f7 Cover viewing different price for different product variants API scenario
This PR was merged into the 1.13 branch.
Discussion
----------
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.13 <!-- see the comment below --> |
| Bug fix? | no |
| New feature? | slighly |
| BC breaks? | no |
| Deprecations? | no <!-- don't forget to update the UPGRADE-*.md file --> |
| License | MIT |
<!--
- Bug fixes must be submitted against the 1.12 branch
- Features and deprecations must be submitted against the 1.13 branch
- Make sure that the correct base branch is set
To be sure you are not breaking any Backward Compatibilities, check the documentation:
https://docs.sylius.com/en/latest/book/organization/backward-compatibility-promise.html
-->
Until now, we were able to see all associated products for a given product, including those that were disabled. With the new implementation, only enabled products are displayed when accesing `ProductAssociation` endpoint
Commits
-------
c9bff1ca15 Cover viewing product associations via API
This PR was merged into the 1.13 branch.
Discussion
----------
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.13
| Bug fix? | no
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Related tickets | contains fixes from #14941
| License | MIT
Commits
-------
b0c17b1f65 Cover inform_customer_about_order_total_changes scenarios in API
c126bf3854 Remove dead code
48a4bdf9a6 Add a past tense for "I proceed through checkout process" step
2a77873fdc Fix CI
This PR was merged into the 1.13 branch.
Discussion
----------
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.13 <!-- see the comment below --> |
| Bug fix? | no |
| New feature? | no |
| BC breaks? | no |
| Deprecations? | no <!-- don't forget to update the UPGRADE-*.md file --> |
| Related tickets | https://github.com/Sylius/Sylius/pull/12633 |
| License | MIT |
<!--
- Bug fixes must be submitted against the 1.12 branch
- Features and deprecations must be submitted against the 1.13 branch
- Make sure that the correct base branch is set
To be sure you are not breaking any Backward Compatibilities, check the documentation:
https://docs.sylius.com/en/latest/book/organization/backward-compatibility-promise.html
-->
Can be safely uncommented as https://github.com/Sylius/Sylius/pull/12633 is no more valid
Commits
-------
Uncomment editing customer profile steps
This PR was merged into the 1.13 branch.
Discussion
----------
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.13 <!-- see the comment below --> |
| Bug fix? | no |
| New feature? | yes |
| BC breaks? | no |
| Deprecations? | no<!-- don't forget to update the UPGRADE-*.md file --> |
| License | MIT |
<!--
- Bug fixes must be submitted against the 1.12 branch
- Features and deprecations must be submitted against the 1.13 branch
- Make sure that the correct base branch is set
To be sure you are not breaking any Backward Compatibilities, check the documentation:
https://docs.sylius.com/en/latest/book/organization/backward-compatibility-promise.html
-->
Shop API coverage
Commits
-------
[Scenario][API] Product variants with options
[Behat][API] Handle query parameters within the client's index method
[Behat][Cart][ProductOptions] Refactor behat context
[Behat] Refactor viewing enabled variants
[Behat][API] Add step implementation for product variants with options
This PR was merged into the 1.13 branch.
Discussion
----------
Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.13 <!-- see the comment below --> |
| Bug fix? | kind of |
| New feature? | yes |
| BC breaks? | no |
| Deprecations? | no<!-- don't forget to update the UPGRADE-*.md file --> |
| Related tickets | https://github.com/Sylius/Sylius/pull/14791 |
| License | MIT |
This PR changes (or more accurately unifies) the way we can delete taxon in Sylius.
Previously, we could delete a taxon that is not `main_taxon` for any product, and we could not delete a taxon in the opposite case.
This PR allows us to remove taxon that is `main_taxon` for some product by setting the relationship to `NULL`.
Alternatively, we could prevent the deletion of taxon in both cases. Let's bring this up for discussion 💬
Commits
-------
[Feature] Add deleting a taxon that is a main taxon of a product scenario
[API][Behat][Taxon] Add step implementation
Revert "[Behat] Describe scenario for messing up products assignments after trying to delete taxon
[Behat][UI] Change isMainTaxonChosen method name
[UI][Behat][Taxon] Add step implementation
[Products] Add ON DELETE SET NULL to the Product mainTaxon field mapping
[Migrations] Alter the product table
This PR was merged into the 1.12 branch.
Discussion
----------
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.12 or 1.13 <!-- see the comment below --> |
| Bug fix? | yes |
| New feature? | no |
| BC breaks? | no |
| Deprecations? | no |
| Related tickets | |
| License | MIT |
I propose this modification, in order that the default shipping method is selected according to the position of the methods in the admin, even when the customer does not have an address yet.
<!--
- Bug fixes must be submitted against the 1.12 branch
- Features and deprecations must be submitted against the 1.13 branch
- Make sure that the correct base branch is set
To be sure you are not breaking any Backward Compatibilities, check the documentation:
https://docs.sylius.com/en/latest/book/organization/backward-compatibility-promise.html
-->
Commits
-------
default shipping methods order by position
Merge branch 'Sylius:1.12' into 1.12
Merge branch 'Sylius:1.12' into 1.12
Behat scenario
Add @api tag
Update features/cart/shopping_cart/resolving_default_shipping_method_in_cart_summary_based_on_method_position.feature
This PR was merged into the 1.13 branch.
Discussion
----------
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.13
| Bug fix? | no
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Related tickets |
| License | MIT
Commits
-------
6426db133e Cover editing customer profile scenarios in API
This PR was merged into the 1.13 branch.
Discussion
----------
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.13
| Bug fix? | no
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Related tickets |
| License | MIT
Commits
-------
5c319cc0b6 Cover product integrity scenarios in API
This PR was merged into the 1.13 branch.
Discussion
----------
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.13
| Bug fix? | no
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Related tickets |
| License | MIT
Commits
-------
69e83ad372 Cover seeing default shipping method scenarios in API
