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

Enhancement: console should be extensible #7

Open
robbieaverill opened this issue Jan 2, 2017 · 2 comments
Open

Enhancement: console should be extensible #7

robbieaverill opened this issue Jan 2, 2017 · 2 comments
Milestone

Comments

@robbieaverill
Copy link
Contributor

robbieaverill commented Jan 2, 2017

As a developer I should be able to add my own commands for the console.

They may live in a user directory, e.g. ~/silverstripe-console/src or in a SilverStripe application folder, e.g. /var/www/silverstripe-console/src

Any configuration YAML files should be merged into the main configuration file before commands are loaded.

We could also search through all vendor/ folders for a ssconsole.yml file to be able to pick up multiple modules installed with composer.

The user directory configuration (e.g. ~/ssconsole.yml) should take priority over custom modules, which should be loaded on top of core commands.

I don't imagine any way initially of being able to modify the core ssconsole behaviour, although we could probably use symfony console events to provide some level of abstraction if we need to.

@robbieaverill
Copy link
Contributor Author

cc @silverleague/console for feedback

@robbieaverill
Copy link
Contributor Author

Not required for initial release, so changing to 1.1.0 milestone

@robbieaverill robbieaverill modified the milestones: 1.0.0, 1.1.0 Jan 25, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants