π§© WP Bones 3.1 β your own stubs
byβ’
WP Bones 3.1 is out 𦴠your generators, your templates π§©
π Your stubs come first. Every make:* command reads the stubs/ folder of your plugin before the framework's, and tells you when it does.
π€ stub:publish copies the framework's stubs there to start from. A stub you edited is kept unless you pass --force.
π¦ deploy leaves them out of the package.

β¬οΈ composer update wpbones/wpbones
π Docs, boilerplates and live Playground demos: https://wpbones.com
Which generator would you change first? π
14 views


Replies
Thanks for another steady update, Giovambattista. Leaving the stubs out of the deploy package is a small thing, but it shows you thought about real use
@katie_schmalzried17Β ππ thx - really appreciated