Skip to content
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mark console commands as final classes #944

Merged
merged 3 commits into from
Mar 20, 2020

Conversation

goetas
Copy link
Member

@goetas goetas commented Mar 12, 2020

Q A
Type improvement
BC Break -
Fixed issues

Summary

Mark console commands as final to avoid extension. Console commands are not meant for that propuse.

@goetas goetas added this to the 3.0.0 milestone Mar 12, 2020
@goetas goetas force-pushed the mark-commands-as-final branch 2 times, most recently from 47cbbc3 to 19780b9 Compare March 12, 2020 21:16
@goetas
Copy link
Member Author

goetas commented Mar 14, 2020

I really don't understand why scrutinizer started to complain lately

@greg0ire
Copy link
Member

Do you mean appveyor?

{
proc_open($editorCommand . ' ' . escapeshellarg($path), [], $pipes);
$process = new Process([$editorCommand, $path]);
$process->setTty(true);
Copy link
Member

Choose a reason for hiding this comment

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

I guess this must be why Appveyor is failing

Copy link
Member Author

Choose a reason for hiding this comment

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

Do you know if the feature of opening an editor works/worked at all on windows systems?

(or was simply never tested...)

If so, can we simply skip the test?

Copy link
Member

Choose a reason for hiding this comment

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

No. (no). Probably, I don't know why an editor is involved here TBH.

Copy link
Member Author

Choose a reason for hiding this comment

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

What about dropping the possibility of opening an editor from doctrine migrations? I think that is out of scope for such library...

Copy link
Member

Choose a reason for hiding this comment

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

Had no idea this was a thing… what is it used for?

Copy link
Member

Choose a reason for hiding this comment

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

Oh ok… well I know I wouldn't use it, because I don't like having many instances of vim running for the same project. In favor of dropping that feature.

Copy link
Member Author

Choose a reason for hiding this comment

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

@alcaeus what do you think?

Copy link
Member

Choose a reason for hiding this comment

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

I've never used it either. If it's causing problems, drop it. If it's easier to skip something on Windows, do that. I don't have any preference here ;)

Copy link
Member Author

Choose a reason for hiding this comment

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

I will drop it then, as it will allow us to not depend on the symfony/process component.

Copy link
Member Author

Choose a reason for hiding this comment

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

done, removed

@goetas
Copy link
Member Author

goetas commented Mar 15, 2020

Do you mean appveyor?

did not realize was appveyor... in the last PR scritinizer complained about something... but it stopped now...

@goetas goetas force-pushed the mark-commands-as-final branch from 5228148 to 33ea68a Compare March 20, 2020 10:51
@goetas
Copy link
Member Author

goetas commented Mar 20, 2020

I think that this is ready.

(still do not know what causes scrutinizer to fail)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants