Hello, folks.
I was wondering, what's your plugin development workflow?
What I know is that before you want to start developing a plugin, you must at least have a surrogate app to write and test it with. From there, you'll want to push it somewhere (probably with a Composer manifest) where another developer can pull it and start using it in their app.
What I'm thinking is, is the "surrogate app" step really necessary? I'm planning to build a plugin right inside the app that intends to use it, rather than writing the plugin in the surrogate app first. Obviously with this approach, I can't directly add the plugin to my consumer app's Composer file, simply because Composer will not let the plugin overwrite itself, and would be extremely funny if Composer did allow it. Any thoughts?
Cheers,
OJ
-- I was wondering, what's your plugin development workflow?
What I know is that before you want to start developing a plugin, you must at least have a surrogate app to write and test it with. From there, you'll want to push it somewhere (probably with a Composer manifest) where another developer can pull it and start using it in their app.
What I'm thinking is, is the "surrogate app" step really necessary? I'm planning to build a plugin right inside the app that intends to use it, rather than writing the plugin in the surrogate app first. Obviously with this approach, I can't directly add the plugin to my consumer app's Composer file, simply because Composer will not let the plugin overwrite itself, and would be extremely funny if Composer did allow it. Any thoughts?
Cheers,
OJ
Like Us on FaceBook https://www.facebook.com/CakePHP
Find us on Twitter http://twitter.com/CakePHP
---
You received this message because you are subscribed to the Google Groups "CakePHP" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cake-php+unsubscribe@googlegroups.com.
To post to this group, send email to cake-php@googlegroups.com.
Visit this group at http://groups.google.com/group/cake-php.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment