-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Merge 2.6 #1518
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
Merged
Merged
Merge 2.6 #1518
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… `2.6` branch (api-platform#1449) Previous URL leads to 404
…latform#1456) Using classic decoration for the custom Data Persister in services.yaml will replace the core persister. Probably this isn't the most common case scenario; normally you would *add* your custom Data Persister to the chain of persisters instead of replacing it. Use attribute binding instead, as already explained in SymfonyCasts' video.
…i-platform#1468) * Replace ORM annotations to PHP attributes * Replace @Orm annotations to PHP attributes * Add #[ORM\Entity] * Correction of #[ORM] attribute * Modification of @Orm\Column to #[ORM\Column] for $email property * Modification of @Assert annotation to #[Assert] attribute * Corrections of PR api-platform#1466 * Docs: update PHP types for property + update old annotations with PHP attributes * Correction of typo : insersedBy to inversedBy * Delete unnecessary parenthesis * Remove type float * Modify targetEntity value * Add Question type * Add Answer type * Delete PHPDoc without @var type * Replace PHP attributes outside annotations * Add string type to $content * Remove targetEntity, mappedBy and inversedBy for OneToOne relation * Remove type DateTimeInterface due to validation test Co-authored-by: Antoine Bluchet <soyuka@users.noreply.github.com>
…te (api-platform#1472) * docs: Add information about how to significantly improve the test suite Hi, this iPR adds an inromation for the page about `JWT` authentication about how to make the tests fast. The issue boils down to the very slow password hashers that are used in tests by default. Each time we start a new project, or review the current one, we have to do it, because tests are extremely slow. This is only one of the many optimizations available for the end developer, but let's start here. Other ones are listed in by blog post: https://maks-rafalko.github.io/blog/2021-11-21/symfony-tests-performance/#using-more-simple-password-hasher * Update wording in core/jwt.md Co-authored-by: Alan Poulain <contact@alanpoulain.eu> Co-authored-by: Alan Poulain <contact@alanpoulain.eu>
Co-authored-by: Antoine Bluchet <soyuka@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.