Skip to content
This repository has been archived by the owner on Jul 5, 2022. It is now read-only.

Symfony 3.4 deprecations (registering commands) #28

Closed
alister opened this issue Oct 19, 2017 · 2 comments
Closed

Symfony 3.4 deprecations (registering commands) #28

alister opened this issue Oct 19, 2017 · 2 comments

Comments

@alister
Copy link
Contributor

alister commented Oct 19, 2017

Auto-registration of the command "DZunke\SlackBundle\Command\BotMessagingCommand" is deprecated since Symfony 3.4

Also for:

  • "DZunke\SlackBundle\Command\ChangeChannelsTopicCommand"
  • "DZunke\SlackBundle\Command\DebugCommand"
  • "DZunke\SlackBundle\Command\MessageCommand"
  • "DZunke\SlackBundle\Command\UsersCommand"

Just being in the Command/ directory is no longer enough. They must also be tagged. This can be done explicitly, listing them in the ./Resources/config/services.yml file, or with Symfony 3.3+ they can also be tagged if they extend a particular class - Symfony\Component\Console\Command\Command is probably best.

@arthens
Copy link

arthens commented Apr 6, 2018

@DZunke it doesn't look like this was ever released. Is there any plan to release version 2.4 (or 3) soon?

@DZunke
Copy link
Owner

DZunke commented Apr 6, 2018

Hey @arthens ,

thanks for the Question. There will be a 3.0 release. It is at the top 3 of my trello cards. so it moved forward the last months. I could do the 3.0 release before my planned small rebuilds for the core if you need a released version with the Current Changelog of Master. It has to be 3.0 cause of the bc break. After 3.0 it maybe it is a good idea to split the master a bit to support better bugfixing.

Ok ... i cannot promise to work on it in the next 3 weeks but if you need the release i could do that first in the near future.

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

No branches or pull requests

3 participants