Open fubarhouse opened 8 years ago
:+1: for this feature.
https://www.drupal.org/node/2573341 is another reason we should think of this sooner, rather than later. If the entity api is improved in a minor revision of d8, then the current solution in the console becomes obsolete. And we need to handle that.
I do not think we should postponed this until we have a stable releasee.
With Drupal 8.1 changing the version of symfony components this will be a good time to analyze this.
Drupal Console v1.0.0-alpha1 is release, providing support for 8.1.x and dropping support for 8.0.1
This is a great time to take a look at this issue and start investigating possibilities.
I've become really fond on version control systems such to the effect of NVM (https://github.com/creationix/nvm), RVM (https://github.com/rvm/rvm), PyEnv (https://github.com/yyuu/pyenv) so much that I've created my own Drush Version Manager (https://github.com/fubarhouse/dvm).
I was wondering publically if this idea would be worthwhile for Drupal Console and it came up positively.
The idea is to be able to change Drupal Console to any particular version for whatever reason be it commands, compatibility, hardware, scripting or preference.
Examples of the commands would be something to the effect of:
drupal console-version 1.0.0
drupal console-version 0.9