Plugin skeleton
Hey everybody!
I'm wondering, if there's an "intelligent" plugin skeleton available. And with "intelligent" I mean something that asks about various aspects of the skeleton (name/author/php classes namespace/should a bootstrap class be created?) and creates them on the fly. Perhaps, together with build automation tools (better changelog, deploying to GitHub, etc.).
If not, I'll create a Yeoman generator for that.
Kind regards
Dennis
Waldbuehne Heessen
Plugin Development
Talking about how to write plugins
- Jeroen Dalsem@jdalsem
Jeroen Dalsem - 0 likes
- Westfälische Freilichtspiele e.V. Waldbühne Heessen@waldbuehne-heessen
Westfälische Freilichtspiele e.V. Waldbühne Heessen - 0 likes
- Jerome Bakker@jeabakker
Jerome Bakker - 0 likes
- Westfälische Freilichtspiele e.V. Waldbühne Heessen@waldbuehne-heessen
Westfälische Freilichtspiele e.V. Waldbühne Heessen - 0 likes
- Westfälische Freilichtspiele e.V. Waldbühne Heessen@waldbuehne-heessen
Westfälische Freilichtspiele e.V. Waldbühne Heessen - 0 likes
- Westfälische Freilichtspiele e.V. Waldbühne Heessen@waldbuehne-heessen
Westfälische Freilichtspiele e.V. Waldbühne Heessen - 0 likes
- Westfälische Freilichtspiele e.V. Waldbühne Heessen@waldbuehne-heessen
Westfälische Freilichtspiele e.V. Waldbühne Heessen - 0 likes
- Pranjal Pandey@pranj7
Pranjal Pandey - 0 likes
You must log in to post replies.There is no such thing at the moment. There was talk about it in the past https://github.com/Elgg/Elgg/issues/9604 but nothing came of it. Feel free to write your yeoman generator. We could even ship it with Elgg...
Will do. Quick question: There isn't currently an API for the plugin library, right? So in the generated plugin I can't include features for automatically uploading the plugin after creating the release on github.
Unfortunately not. This is on our wish list as well. But time is a limiting factor.
Maintaining plugins on GitHub / Packagist is easy. Only keeping the community version of the plugin up-to-date is still a manual step.
Okay. Thanks.
Oh, one suggestion: You should use SPDX license identifiers in the plugin registry (https://spdx.org/licenses/) That would make it more compatible with composer.json.
Done. :) Check out the workflow:
@Jerome I've uploaded the result of the generator here:
https://drive.google.com/file/d/1fKIRk0bXuUYzugRZUOVB40QXxUJF6uCY/view?usp=sharing
Could you please check it out and see if you find any errors?
If it is usable, I'd release 1.0.0 as an npm package and it can be used then.
Dennis
@Jerome ping :)
If some one laded here looking for simple plugin skeleton , I did make small bash script to generate one:
https://gist.github.com/physcocode/6f7be87046f5dc9a41f751cd52cb3662