* 2.0: (26 commits)
Update namespaces to Resource ^1.11 in 2.0
[CS][DX] Refactor
[CS][DX] Refactor
[Maintenance] Update resource changes comparison in the upgrade file
[Maintenance] Fix LazyOption repository template covariants
[Maintenance] Note resource namespaces changes
[Docs] Update namespaces
[Maintenance] Update leftover namespaces
Cover the scenario for allowing access for only correctly logged in users
Enable the remaining cart suites
[Maintenance] Fix translations' duplicated validation
[Api][Unit] Fix it_gets_all_product_variants_when_invalid_product_filter_provided test
[Api] Replace sylius.api to sylius_api
[Api] Cover sorting and filtration of resources
[Behat] Refine codebase for promotion and cart contexts
Enable dashboard and homepage suites
Minor Product config improvement
Enable the rest of product tests and correct order of the attribute values in the response
Correct contract tests and behat
Bring back non exposed ProductOptionValue
...
| Q | A
|-----------------|-----
| Branch? | 2.0 <!-- 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
TODO: Cover these scenarios
eb0a19aacb
<!--
- 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
-->
This PR has been generated automatically.
For more details see
[upmerge_pr.yaml](/Sylius/Sylius/blob/1.13/.github/workflows/upmerge_pr.yaml).
**Remember!** The upmerge should always be merged with using `Merge pull
request` button.
In case of conflicts, please resolve them manually with usign the
following commands:
```
git fetch upstream
gh pr checkout <this-pr-number>
git merge upstream/payment-request -m "Resolve conflicts between 2.0 and payment-request"
```
If you use other name for the upstream remote, please replace `upstream`
with the name of your remote pointing to the `Sylius/Sylius` repository.
Once the conflicts are resolved, please run `git merge --continue` and
push the changes to this PR.
* 2.0:
[Api][Unit] Fix it_gets_all_product_variants_when_invalid_product_filter_provided test
[Api] Replace sylius.api to sylius_api
[Api] Cover sorting and filtration of resources
* 2.0:
[Behat] Refine codebase for promotion and cart contexts
Enable dashboard and homepage suites
Minor Product config improvement
Enable the rest of product tests and correct order of the attribute values in the response
Correct contract tests and behat
Bring back non exposed ProductOptionValue
[Behat] Refine flow of shop promotion scenarios
| Q | A
|-----------------|-----
| Branch? | api-platform-3 <!-- see the comment below -->
| Bug fix? | no
| New feature? | no
| BC breaks? | no
| 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? | api-platform-3
| Bug fix? | no
| New feature? | no
| BC breaks? | no
| Deprecations? | no <!-- don't forget to update the UPGRADE-*.md file
-->
| Related tickets |
| 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? | api-platform-3
| Bug fix? | no
| New feature? | no
| BC breaks? | no
| Deprecations? | no<!-- don't forget to update the UPGRADE-*.md file
-->
| Related tickets |
| 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? | api-platform-3
| Bug fix? | no
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Related tickets |
| License | MIT
TODO:
- [ ] adjust Behat scenarios
<!--
- 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
-->
