A few of you have been asking about some of the Known dev tools that I use.
Well, I’ve been writing them as I go, and they’re a little bit dotted around, but since moving to composer I’ve been trying to link them up a bit.
Known Dev Scripts
The main dev scripts that I’ve been using are here. Requiring this package will also fetch the language tools scripts and the PHPCS code formatter config.
All of these are already included in the Known checkout in the
vendor directory, if you’re checking out from git, and composer installing the dev dependencies (default).
composer require mapkyca/known-dev-scripts --dev
Next are a set of console tools that I’ve built up over time which give me some ability to nudge data around, and to get various dumps of raw data.
They’re dotted around in their own repos, and can be installed individually, but for convenience you can grab them all in one go:
composer require mapkyca/known-console-tools --dev
It goes without saying that these should not be installed on a production system – with great power, and all that.
Recently, the Composer Installers project added support for Known, which opened up the exciting possibility of using Composer to deliver Known plugins and Themes.
Those of you who are tracking GitHub, you might have noticed that all the plugins and themes have disappeared!
Fear not, however. They are now all in their own repositories and installable via composer.
This is pretty cool, as not only does this solve some of the distribution and directory naming issues we were having (since now, composer manages both the downloading and making sure the plugin is installed to the correct location), but it also makes it super easy to role custom builds of Known with just a change to one file!
Having the plugins in their own repos will also hopefully make it much less daunting for people to get involved with development.
I’ve written before how package authors can update their stuff to take advantage of this, but I’ve already updated most of the core plugins and themes.
Just a quick one, I’ve just updated the Known dev tools with a new script –
There’s currently only one function available
enable-composer which, following my last post, provides a handy script for making your plugin composer installable.
Run the script, passing it the repository you’ve saved it as (so that the script can set the packagist headers correctly), and you’ll get an updated / new
composer.json with all the appropriate values set.
You can optionally set whether the plugin is a straight plugin, theme or console plugin (known-plugin is default). You can also target directories other than the current directory, although realistically you’re never really going to run it from any other directory.
» Visit the project on Github...