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

[FrameworkBundle][Workflow] Fix deprectation when checking workflow.registry service in dump command#24620

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

Closed
Jean-Beru wants to merge5 commits intosymfony:3.4fromJean-Beru:fix-workflow-private-service-check
Closed

[FrameworkBundle][Workflow] Fix deprectation when checking workflow.registry service in dump command#24620

Jean-Beru wants to merge5 commits intosymfony:3.4fromJean-Beru:fix-workflow-private-service-check

Conversation

@Jean-Beru
Copy link
Contributor

@Jean-BeruJean-Beru commentedOct 19, 2017
edited
Loading

QA
Branch?3.4
Bug fix?yes
New feature?no
BC breaks?no
Deprecations?no
Tests pass?yes
Fixed tickets
LicenseMIT
Doc PR

This PR will declareworkflow.registry as a public service to avoid deprecation whenWorkflowDumpCommand checks its existence. It only concerns 3.4 since thisisEnabled method will be removed in 4.0.

@stof
Copy link
Member

Well, forcing to keep the service as public just for the BC layer is bad, as it means that any people using the service in a public way would not be warned about that (and so we cannot make the service private at all in 4.0).

A better solution would be to improve the way the command gets disabled in 3.4.

@nicolas-grekasnicolas-grekas added this to the3.4 milestoneOct 19, 2017

<serviceid="workflow.security.expression_language"class="Symfony\Component\Workflow\EventListener\ExpressionLanguage" />

<serviceid="Symfony\Bundle\FrameworkBundle\Command\WorkflowDumpCommand">
Copy link
Contributor

Choose a reason for hiding this comment

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

moving this requires$container->removeDefinition(WorkflowDumpCommand::class); call to be updated, as console.xml is also conditionally loaded.

Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

Nice catch ;-)

Copy link
Contributor

Choose a reason for hiding this comment

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

well it still needs to be removed if console is not available ;-) not sure about the current effect of this service without console available. I guess it doesnt hurt.

Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

Argh! I think we can keep command definition inconsole.xml and remove it if workflow is disabled.

@Jean-Beru
Copy link
ContributorAuthor

Thanks for your feedback@stof. So, I moved command in the conditionnally loadedworkflow.xml.

@Jean-BeruJean-Beru changed the title[Workflow] Fix deprectation when checking workflow.registry service in dump command[FrameworkBundle][Workflow] Fix deprectation when checking workflow.registry service in dump commandOct 20, 2017
Copy link
Member

@nicolas-grekasnicolas-grekas left a comment

Choose a reason for hiding this comment

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

(with minor comment)

{
if (!$config['enabled']) {
if (!class_exists(Workflow\Workflow::class)) {
if ($container->hasDefinition(WorkflowDumpCommand::class)) {

Choose a reason for hiding this comment

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

the "if" can be removed: removeDefinition already does it internally

Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

Correct. Thks@nicolas-grekas !

@fabpot
Copy link
Member

Thank you@Jean-Beru.

@fabpotfabpot closed thisOct 20, 2017
fabpot added a commit that referenced this pull requestOct 20, 2017
… workflow.registry service in dump command (Jean-Beru)This PR was squashed before being merged into the 3.4 branch (closes#24620).Discussion----------[FrameworkBundle][Workflow] Fix deprectation when checking workflow.registry service in dump command| Q             | A| ------------- | ---| Branch?       | 3.4| Bug fix?      | yes| New feature?  | no <!-- don't forget to update src/**/CHANGELOG.md files -->| BC breaks?    | no| Deprecations? | no <!-- don't forget to update UPGRADE-*.md files -->| Tests pass?   | yes| Fixed tickets || License       | MIT| Doc PR        |This PR will declare `workflow.registry` as a public service to avoid deprecation when `WorkflowDumpCommand` checks its existence. It only concerns 3.4 since this `isEnabled` method will be removed in 4.0.Commits-------9e75847 [FrameworkBundle][Workflow] Fix deprectation when checking workflow.registry service in dump command
This was referencedOct 30, 2017
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@fabpotfabpotfabpot approved these changes

@nicolas-grekasnicolas-grekasnicolas-grekas approved these changes

@chalasrchalasrchalasr approved these changes

+1 more reviewer

@ro0NLro0NLro0NL approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Projects

None yet

Milestone

3.4

Development

Successfully merging this pull request may close these issues.

7 participants

@Jean-Beru@stof@fabpot@nicolas-grekas@ro0NL@chalasr@carsonbot

[8]ページ先頭

©2009-2025 Movatter.jp