* 1.14:
[Documentation] Fix 2.0-dev installation instruction tip
Improve DefaultChannelFactory test service + add note about change
[Behat] Dehardcode the use of ShopBillingData entity
[Behat] Dehardcode the use of AvatarImage entity
[Admin] Deprecate NotificationWidgetExtension
* 1.14:
[Admin] Pass admin path name parameter to AdminUriBasedSectionResolver
Update docs/customization/api/adding_and_removing_endpoints.rst
Apply suggestions from code review
[API] Refactor statistics constraints
[Promotion] Add missing AsCatalogPromotionVariantChecker attribute
[Core] Add missing type to AsCatalogPromotionPriceCalculator attribute
doc: Adding a tip about api's preventing methods beside GET to load non cart orders by default
* 1.13:
[Admin] Pass admin path name parameter to AdminUriBasedSectionResolver
Update docs/customization/api/adding_and_removing_endpoints.rst
Apply suggestions from code review
[API] Refactor statistics constraints
doc: Adding a tip about api's preventing methods beside GET to load non cart orders by default
| Q | A
|-----------------|-----
| Branch? | 1.13
| Bug fix? | no
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Related tickets | na
| License | MIT
<!--
- Bug fixes must be submitted against the 1.13 branch
- Features and deprecations must be submitted against the 1.14 branch
- Features, removing deprecations and BC breaks must be submitted
against the 2.0 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
-->
Hello,
If we add a custom API endpoint to the Orders using any method besides
GET, we end up with a very unclear 404 error.
Investigating this led us to find this "feature" which prevents us from
loading the order with a given token due to the order not being in the
state `cart`. In our case, we needed to update the customer cart with
information from an older order. So it was logical for us to use `POST`
as we are updating the cart, and it was logical to have the order token
in the URL to specify the order we need to pull the data from.
It was therefore quite frustrating to debug; I thought adding a little
tip about it in the docs wouldn't hurt any future developer coming
across this issue.
Reference to the class where this filtering is done:
https://github.com/Sylius/Sylius/blob/2.0/src/Sylius/Bundle/ApiBundle/Doctrine/ORM/QueryExtension/Shop/Order/StateBasedExtension.php
Hope I contributed as needed, with ❤️
Regards
* 1.14:
[Admin] Deprecate NotificationController
[AdminBundle] Add base form type for ShopUserType
[AdminBundle] Add base form type for PromotionCouponGeneratorInstructionType
chore(doc): add naming changes for plugin skeleton
Add tests kernel and console naming changes.
| Q | A
|-----------------|-----
| Branch? | 1.14
| Bug fix? | no
| New feature? | no
| BC breaks? | no
| Deprecations? | no<!-- don't forget to update the UPGRADE-*.md file
-->
| Related tickets | fixes #X, partially #Y, mentioned in #Z
| License | MIT
<!--
- Bug fixes must be submitted against the 1.13 branch
- Features and deprecations must be submitted against the 1.14 branch
- Features, removing deprecations and BC breaks must be submitted
against the 2.0 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
-->
| Q | A
|-----------------|-----
| Branch? | 2.0
| Bug fix? | no
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Related tickets | n/a
| License | MIT
<!--
- Bug fixes must be submitted against the 1.13 branch
- Features and deprecations must be submitted against the 1.14 branch
- Features, removing deprecations and BC breaks must be submitted
against the 2.0 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
-->
| Q | A
|-----------------|-----
| Branch? | 2.0
| Bug fix? | no
| New feature? | no
| BC breaks? | yes
| Deprecations? | no
| Related tickets | n/a
| License | MIT
<!--
- Bug fixes must be submitted against the 1.13 branch
- Features and deprecations must be submitted against the 1.14 branch
- Features, removing deprecations and BC breaks must be submitted
against the 2.0 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
-->
| Q | A
|-----------------|-----
| Branch? | 2.0
| Bug fix? | no
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Related tickets |
| License | MIT
<!--
- Bug fixes must be submitted against the 1.12 or 1.13 branches
- Features and deprecations must be submitted against the 1.14 branch
- Features, removing deprecations and BC breaks must be submitted
against the 2.0 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
-->
