Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

[DoctrineBridge] Document the newentityClass option#7057

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged

Conversation

ogizanagi
Copy link
Contributor

Waiting forsymfony/symfony#15002 to be merged.

chalasr and yceruto reacted with thumbs up emoji

**type**: ``string`` **default**: ``null``

The fully-qualified class name (FQCN) of the entity to get the repository used for making the query to determine
Copy link
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

I don't like this sentence very much. Any hint on how to rephrase it better ? 😄

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Maybe

The fully-qualified class name (FQCN) of the entity for which to get the repository used to determine the uniqueness

? Or just keep it as is for consistency

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Here is a proposal that says exactly the same but in a different order:

By default, the query performed to ensure the uniqueness uses the repository ofthe current class instance. However, in some cases, such as when using Doctrineinheritance mapping, you need to execute the query in a different repository.Use this option to define the fully-qualified class name (FQCN) of the Doctrineentity associated with the repository you want to use.

ogizanagi and yceruto reacted with thumbs up emoji
Copy link
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

@javiereguiluz : Perfect ! I'll update this PR in the minute. Thank you 🎉

@ogizanagiogizanagiforce-pushed the3.2/feature/select_repo_option branch fromfc063f2 to8e4e47aCompareOctober 13, 2016 17:06
fabpot added a commit to symfony/symfony that referenced this pull requestOct 14, 2016
…ed by the UniqueEntity validator (ogizanagi)This PR was merged into the 3.2-dev branch.Discussion----------[DoctrineBridge] Add a way to select the repository used by the UniqueEntity validator| Q             | A| ------------- | ---| Bug fix?      | no| New feature?  | yes| BC breaks?    | no| Deprecations? | no| Tests pass?   | yes| Fixed tickets |#12573,#4087,#12977| License       | MIT| Doc PR        |symfony/symfony-docs#7057This is a cherry pick of#12977 on ~~2.8~~ 3.2 branch, as it is clearly a new feature, even if it was primary introduced in order to fix an inappropriate behavior that might be considered as a bug.Commits-------00d5459 [Doctrine] [Bridge] Add a way to select the repository used by the UniqueEntity validator
symfony-splitter pushed a commit to symfony/doctrine-bridge that referenced this pull requestOct 14, 2016
…ed by the UniqueEntity validator (ogizanagi)This PR was merged into the 3.2-dev branch.Discussion----------[DoctrineBridge] Add a way to select the repository used by the UniqueEntity validator| Q             | A| ------------- | ---| Bug fix?      | no| New feature?  | yes| BC breaks?    | no| Deprecations? | no| Tests pass?   | yes| Fixed tickets | #12573, #4087, #12977| License       | MIT| Doc PR        |symfony/symfony-docs#7057This is a cherry pick of #12977 on ~~2.8~~ 3.2 branch, as it is clearly a new feature, even if it was primary introduced in order to fix an inappropriate behavior that might be considered as a bug.Commits-------00d5459 [Doctrine] [Bridge] Add a way to select the repository used by the UniqueEntity validator
@ogizanagiogizanagiforce-pushed the3.2/feature/select_repo_option branch from8e4e47a toa9c2fc2CompareOctober 14, 2016 07:15
@ogizanagi
Copy link
ContributorAuthor

PR updated according to@javiereguiluz 's suggestion. The PR on the code repository has been merged too.

@ogizanagiogizanagi changed the title[WCM][DoctrineBridge] Document the newentityClass option[DoctrineBridge] Document the newentityClass optionOct 14, 2016
@xabbuhxabbuh added this to the3.2 milestoneOct 14, 2016
@xabbuhxabbuh removed the On hold labelOct 14, 2016
@wouterj
Copy link
Member

👍
status: reviewed

@javiereguiluz
Copy link
Member

👍

@wouterjwouterj merged commita9c2fc2 intosymfony:masterNov 10, 2016
wouterj added a commit that referenced this pull requestNov 10, 2016
…(ogizanagi)This PR was merged into the master branch.Discussion----------[DoctrineBridge] Document the new `entityClass` optionWaiting forsymfony/symfony#15002 to be merged.Commits-------a9c2fc2 [DoctrineBridge] Document the new `entityClass` option
wouterj added a commit that referenced this pull requestNov 10, 2016
@wouterj
Copy link
Member

Thanks@ogizanagi! Prefect PR!

I've moved the versionadded directives directly after the title, as this is consistent with the versionadded directives in form types options.

ogizanagi and xabbuh reacted with thumbs up emoji

@ogizanagiogizanagi deleted the 3.2/feature/select_repo_option branchNovember 10, 2016 20:09
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@javiereguiluzjaviereguiluzjaviereguiluz left review comments

@chalasrchalasrchalasr left review comments

Assignees
No one assigned
Projects
None yet
Milestone
3.2
Development

Successfully merging this pull request may close these issues.

6 participants
@ogizanagi@wouterj@javiereguiluz@chalasr@xabbuh@carsonbot

[8]ページ先頭

©2009-2025 Movatter.jp