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] fix yaml:lint when yaml is not installed along side framework-bundle#20066

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
fabpot merged 1 commit intosymfony:masterfromfabpot:yaml-command
Sep 28, 2016

Conversation

@fabpot
Copy link
Member

QA
Branch?master
Bug fix?yes
New feature?no
BC breaks?no
Deprecations?no
Tests pass?yes
Fixed ticketsn/a
LicenseMIT
Doc PRn/a

YAML is not an explicit dependency of FrameworkBundle. If it is not installed, the console is broken as the yaml:lint commands tries to extends the one in the YAML component. This bug only exists in master as this refactoring happened in 3.2

chalasr reacted with thumbs up emoji
parent::configure();
$this->setName('lint:yaml');

if (!$this->isEnabled() &&null !==$this->command) {
Copy link
Member

Choose a reason for hiding this comment

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

Do we need this?configure() should never be called if the command is not enabled.

Copy link
MemberAuthor

Choose a reason for hiding this comment

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

Yes, this is needed asconfigure() is called by the constructor.

@javiereguiluzjaviereguiluz changed the title[FrameworkBundle] fix yaml:lint when yaml is not installed along side framwork-bundle[FrameworkBundle] fix yaml:lint when yaml is not installed along side framework-bundleSep 28, 2016
private$directoryIteratorProvider;
private$isReadableProvider;

publicfunction__construct($name =null,$directoryIteratorProvider =null,$isReadableProvider =null)
Copy link
Member

Choose a reason for hiding this comment

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

Couldn't$directoryIteratorProvider and$isReadableProvider be type-hinted ascallable?

Copy link
MemberAuthor

Choose a reason for hiding this comment

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

They could

}

returnparent::getDirectoryIterator($directory);
returnclass_exists('Symfony\Component\Yaml\Command\LintCommand') &&parent::isEnabled();
Copy link
Member

Choose a reason for hiding this comment

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

Could beclass_exists(BaseLintCommand::class)

Copy link
MemberAuthor

Choose a reason for hiding this comment

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

done

@fabpotfabpot merged commitb1c5a68 intosymfony:masterSep 28, 2016
fabpot added a commit that referenced this pull requestSep 28, 2016
… along side framework-bundle (fabpot)This PR was merged into the 3.2-dev branch.Discussion----------[FrameworkBundle] fix yaml:lint when yaml is not installed along side framework-bundle| Q             | A| ------------- | ---| Branch?       | master| Bug fix?      | yes| New feature?  | no| BC breaks?    | no| Deprecations? | no| Tests pass?   | yes| Fixed tickets | n/a| License       | MIT| Doc PR        | n/aYAML is not an explicit dependency of FrameworkBundle. If it is not installed, the console is broken as the yaml:lint commands tries to extends the one in the YAML component. This bug only exists in master as this refactoring happened in 3.2Commits-------b1c5a68 [FrameworkBundle] fixed yaml:lint when yaml is not installed along side framwork-bundle
@fabpotfabpot deleted the yaml-command branchSeptember 28, 2016 14:38
@fabpotfabpot mentioned this pull requestOct 27, 2016
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@xabbuhxabbuhxabbuh left review comments

@chalasrchalasrchalasr left review comments

Assignees

No one assigned

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@fabpot@xabbuh@chalasr@carsonbot

[8]ページ先頭

©2009-2025 Movatter.jp