Update of ProductReviews state machine name that is used in example. Currently not existing name (sylius_review) is used to show on how to modify existing callback with existing state machine
Should be sylius_product_review
This PR was merged into the 1.13 branch.
Discussion
----------
fix typo
| Q | A
|-----------------|-----
| Branch? | 1.12, 1.13, 1.14 or 2.0 <!-- see the comment below -->
| Bug fix? | no/yes
| New feature? | no/yes
| BC breaks? | no/yes
| Deprecations? | no/yes <!-- 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.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
-->
Commits
-------
cfcbd05dec Update repository.rst
This PR was merged into the 1.13 branch.
Discussion
----------
fix typo
| Q | A
|-----------------|-----
| Branch? | 1.12, 1.13, 1.14 or 2.0 <!-- see the comment below -->
| Bug fix? | no/yes
| New feature? | no/yes
| BC breaks? | no/yes
| Deprecations? | no/yes <!-- 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.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
-->
Commits
-------
74a900caa8 Update model.rst
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
git merge upstream/1.13 --no-commit
```
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
change the commit title to
```
Resolve conflicts between 1.12 and 1.13
```
* 1.12:
Avoid double label translation
Replace http with https
Replace http with https
Replace Doctrine Persistence Object Manager API docs URL to another reference in the docs, since the former was removed (see https://twitter.com/doctrineproject/status/1116080889996431362)
fix Symfony XML schema namespace
Update spreecommerce adjustments docs URL
fix Symfony XML schema namespace
Replace Doctrine ORM Query Builder API docs URL to another reference in the docs, since the former was removed (see https://twitter.com/doctrineproject/status/1116080889996431362)
Update spreecommerce inventory docs URL
Update spreecommerce adjustments docs URL
Update spreecommerce products docs URL
Update spreecommerce taxonomies and taxons user docs URL
Replace dead Payum URL with its GitHub repo URL
Remove references to api.sylius.com which was shut down
remove dead link to codebetter.com
fix message of the length constraint on email
This PR was merged into the 1.13 branch.
Discussion
----------
| Q | A
| --------------- | -----
| Branch? | 1.13
| Bug fix? | no
| New feature? | yes
| BC breaks? | no
| Deprecations? | no
| Related tickets | blocked by #12556
| License | MIT
Commits
-------
c3a36e9b6c Add documentation for non-labeled actions
730ee59cc7 Apply suggestions from code review
Co-authored-by: Magdalena Sadowska <bannanowa@gmail.com>
c7349d3198 Fix labeled
* 1.11:
Use tokenValue instead of id
[Hot-fix] Conflict with the newest AP that changes a Customer->User response
small PR fix
[DOCS] Add info about mailer in installation doc
Using the new template namespace syntax in the doc
This PR was merged into the 1.12 branch.
Discussion
----------
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.12 <!-- 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 | |
| License | MIT |
<!--
- Bug fixes must be submitted against the 1.11 branch
- Features and deprecations must be submitted against the 1.12 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
-->
Initially, I was planning to make a bigger section about our changes in frontend but I think the section from the `UPGRADE` file is more than enough (ref https://github.com/Sylius/Sylius/pull/14330).
Commits
-------
02d6a7b050 Remove migrating to webpack page from docs
8af27a6e6b Update documentation about Frontend
* Using the correct syntax highlighting language (eg. using twig instead of html)
* Fixing the indentation of one of the curl calls
* Using the correct comments (// in yaml is not a valid comment)
* 1.10:
Minimize number of build for packages
[Maintenance] Conflict with Symfony ^6.0
[Minor] Fix CONFLICT.md lining
feature #13339 Add Support for Symfony 5.4 (AdamKasp)
[Maintanance] add conflict
Corrections for adding a field to the response
I was implementing my own ProductNormalizer and found some issues in the docs:
1. The example used the NormalizerAwareTrait, but for autowiring constructor injection might be easier.
2. It was not clear in the example which service I had to inject for the normalizer, turns out it was `@api_platform.serializer.normalizer.item`
3. The example referenced a `defaultProductVariantResolver`, but that property did not exist, so I added it.
