You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 5, 2022. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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 freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Auto-registration of the command "DZunke\SlackBundle\Command\BotMessagingCommand" is deprecated since Symfony 3.4
Also for:
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.The text was updated successfully, but these errors were encountered: