Thanks to visit codestin.com
Credit goes to github.com

Skip to content

[Phpspec] add a missing scenario on customer context spec #9932

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.

Sign up for GitHub

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

Jump to bottom
Merged
Zales0123 merged 1 commit into from
Nov 20, 2018
Merged

[Phpspec] add a missing scenario on customer context spec #9932

Zales0123 merged 1 commit into from
Nov 20, 2018

Conversation

@loic425
Copy link
Member

@loic425 loic425 commented Nov 16, 2018

Q A
Branch? 1.2
Bug fix? no
New feature? no
BC breaks? no
Deprecations? no
Related tickets
License MIT

I've seen this missing scenario while running it with a phpspec code-coverage extension :)

@loic425 loic425 requested a review from a team as a code owner November 16, 2018 15:54
@loic425 loic425 changed the title add a missing scenario on customer context spec [Phpspec] add a missing scenario on customer context spec Nov 16, 2018
@Zales0123 Zales0123 added the Enhancement Minor issues and PRs improving the current solutions (optimizations, typo fixes, etc.). label Nov 16, 2018
@Zales0123 Zales0123 merged commit a2faf7f into Sylius:1.2 Nov 20, 2018
@Zales0123
Copy link
Contributor

Zales0123 commented Nov 20, 2018

Thank you, Loïc! 🎉

@loic425 loic425 deleted the phpspec/customer-context-spec branch November 20, 2018 14:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

1 more reviewer

@Zales0123 Zales0123 Zales0123 approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

Enhancement Minor issues and PRs improving the current solutions (optimizations, typo fixes, etc.).

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@loic425 @Zales0123