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 guard expressions#28018

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

Conversation

@destillat
Copy link
Contributor

@destillatdestillat commentedJul 20, 2018
edited
Loading

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

Possible fix for#28007 (comment)

$this->transition = $transition;
$this->expression = $expression;
}
} No newline at end of file

Choose a reason for hiding this comment

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

missing EOL. Also please remove all docblocks in this class: they don't provide anything on top of the existing type declaration, and our policy is to not add them in this situation.

@destillat
Copy link
ContributorAuthor

After applying cs changes proposed by fabbot.io there are some conflicts with master branch. Should i merge them?

@nicolas-grekas
Copy link
Member

please rebase instead of merging yes

@destillatdestillatforce-pushed thefix/workflow-guard-expressions branch froma7fe7ea to720f943CompareJuly 26, 2018 11:50
@fabpot
Copy link
Member

@lyrixx Can you review this one? Thank you.

@nicolas-grekas
Copy link
Member

friendly ping@lyrixx

@lyrixx
Copy link
Member

Hello. Sorry for the very late reply. I will have a look tomorrow or after tomorrow. Thanks

@lyrixx
Copy link
Member

Thanks a lot@destillat. I finished you work in#29137 and I rebased against 3.4.
I'm closing this issue in favor my PR

@lyrixxlyrixx closed thisNov 8, 2018
lyrixx added a commit that referenced this pull requestNov 13, 2018
…ansitions (destillat, lyrixx)This PR was merged into the 3.4 branch.Discussion----------[Workflow][FrameworkBundle] fixed guard event names for transitions| Q             | A| ------------- | ---| Branch?       | 3.4| Bug fix?      | yes| New feature?  | no| BC breaks?    | no| Deprecations? | no| Tests pass?   | yes| Fixed tickets |#28018#28007 (comment)| License       | MIT| Doc PR        |There is a bug when many transitions are defined with the same name.I finished destillat's work and rebase against 3.4 as it's a bug fix.There another point of failure, but it could not be fixed on 3.4. I willbe a need feature. The issue is related to `Workflow::can($subject, $transitionName)`.Since the transitionName could be not unique, we will need to supportpassing an instance of Transition. A new PR is incommingCommits-------83dc473 [FrameworkBundle] fixed guard event names for transitionsfb88bfc [FrameworkBundle] fixed guard event names for transitions
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@nicolas-grekasnicolas-grekasnicolas-grekas left review comments

@lyrixxlyrixxAwaiting requested review from lyrixx

Assignees

No one assigned

Projects

None yet

Milestone

3.4

Development

Successfully merging this pull request may close these issues.

5 participants

@destillat@nicolas-grekas@fabpot@lyrixx@carsonbot

[8]ページ先頭

©2009-2025 Movatter.jp