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

META: Robo 2.0.0 aspirational goals #548

Open
5 of 13 tasks
greg-1-anderson opened this issue Mar 21, 2017 · 2 comments
Open
5 of 13 tasks

META: Robo 2.0.0 aspirational goals #548

greg-1-anderson opened this issue Mar 21, 2017 · 2 comments

Comments

@greg-1-anderson
Copy link
Member

greg-1-anderson commented Mar 21, 2017

Goal: Remain mostly backwards compatible with Robo 1.x, and require only minimal changes to clients. Add new deprecations to give folks more time to adjust before any feature is removed.

  • Drop support for PHP 5.x. (Drop php 5 #823)
  • Drop support for Symfony 2 (most clients should be unaffected) (Drop php 5 #823)
  • Fix PSR-2 coding violations (requires renaming loadTasks to LoadTasks or Tasks. Folks who reference only LoadAllTasks or Robo\Tasks should not notice)
  • Factor Config class into consolidation/config and enhance
  • Plugin support
  • Drop support for "shebang" files (see g1a/starter)
  • Make Application the class instantiated by derived apps instead of Runner (minor changes required for all Robo as a Framework clients)
  • Improve handling of $input and $output
    • Avoid caching $input and $output anywhere in the DI container or objects stored in the container (may not be possible; alternative is to deprecate all usage of same)
    • Allow SymfonyStyle to be passed to commands, not just $input and $output; use logger manager (Improved param injection #822)
    • Use SymfonyStyle instead of logger in TaskIO (most clients should be unaffected)
    • Improve appearance of output (Improve Output #858)
  • Clean up Collections

Drupal 8 will drop support for PHP 5.5 and 5.6 on March 6, 2019. Having a Robo 2.x out around this time could be convenient.

@koppieesq
Copy link

Task for Jordan: pull all subtasks into Project

@koppieesq
Copy link

Correction: the only subtasks that exist as separate issues are the ones that are already done. I'll hold off on creating new issues until someone is actually ready to work on them.

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

No branches or pull requests

2 participants