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

Remove the deprecated command interface #22

Merged
merged 4 commits into from
Mar 30, 2015

Conversation

rosstuck
Copy link
Member

As per thephpleague/tactician#43 and thephpleague/tactician#45

@sagikazarmark Thoughts? The stdClass mock is a little ugly, could create a specific fixture for it if you prefer.

@rosstuck
Copy link
Member Author

Also, this is tested with a local dev version of tactician, so this'll fail until Tactician 0.4 is released. I haven't pushed that out yet because it might break folks stuff until we get all the plugins ready to update as well.

@sagikazarmark
Copy link
Member

Personally I like that interface. It makes a command a command.

However I see the point why the interface could be removed. It could also make handling commands easier in some cases (for example we wouldn't need a QueueableCommand interface for the Bernard plugin, we can use Bernard\Message)

But I have to think about this. There are many things to consider.

Yeah, that stdClass thing hurts my eyes. 💯 👎

As for the release: we agreed that until a major release we depend on MJZ releases in plugins (^0.3 now), so it won't break anything. I think it would be better to release the new version, and update plugins later.

@sagikazarmark
Copy link
Member

A command stub would be better for this purpose

@@ -25,7 +25,7 @@
},
"extra": {
"branch-alias": {
"dev-master": "0.3-dev"
"dev-master": "0.4-dev"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you want to align the versions between plugins and the main repo? I don't think it is a good idea. (In the case this is a mistake: 0.3 is the next IIRC)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Whoops, my mistake. 10th repo of the day. 😅

@rosstuck
Copy link
Member Author

About the composer version, I bumped it to 0.4 to be more explicit since removing the Command interface means changing the Middleware typehint and thus triggering an error. If someone is running lowest deps or we're testing against them, they'll always break now: this PR makes it completely unable to work with Tactician 0.3, unfortunately.

@rosstuck
Copy link
Member Author

@sagikazarmark I still need to send a PR for command events or would you rather pick it up? If you'd like me to do it, then let me know how you prefer to setup the stubs (empty interfaces under spec dir, I'm guessing) and I'll pick it up from there.

@sagikazarmark
Copy link
Member

I don't think backwards incompatibility is a problem now. Tactician and the plugins are not stable yet.

I will handle command events. Thanks.

sagikazarmark added a commit that referenced this pull request Mar 30, 2015
…face

Remove the deprecated command interface
@sagikazarmark sagikazarmark merged commit 6dcbc4e into master Mar 30, 2015
@sagikazarmark sagikazarmark deleted the feature/remove-command-interface branch March 30, 2015 14:29
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

Successfully merging this pull request may close these issues.

2 participants