Fixing setup command.

[weerd]

What's this PR do?

This pull request updates the SetupCommand() to fix an issue I ran into when running php artisan rogue:setup after a complete reset of my Homestead.

Seems like the signature of the runCommand() has changed and now requires passing a class that implements the OutputInterface as the third argument.

I figured the simplest way to resolve this would be to use the call() command before hand and precede it with calling the line() command to write the message to the console.

How should this be reviewed?

👀

Any background context you want to provide?

It may be that we'll need to update the other projects that have their own Artisan setup command, since they likely also call the runCommand() as well.

Relevant tickets

🌵

Checklist

• This PR has been added to the relevant Pivotal card.
• Documentation added for new features/changed endpoints.
• Added appropriate feature/unit tests.

[lindsayrmaher]

I updated my homestead and reset up Rogue last week and didn't run into this issue. but i also didn't use the php artisan rogue:setup command. But this seems like a reasonable update to make!

[lindsayrmaher]

🧼

[weerd]

I updated my homestead and reset up Rogue last week and didn't run into this issue. but i also didn't use the php artisan rogue:setup command. But this seems like a reasonable update to make!

Ah yeah, it defs requires running the setup command to run into this error. How did you set up Rogue without it? Just doing the steps it does manually?

[lindsayrmaher]

How did you set up Rogue without it? Just doing the steps it does manually?

Yup yupp!