We don’t actually have the example docs for how to disable this module and that the key is actually search. We were going to rename this module to search but that fell off the radar. We can do that properly in the next version, but search will be the correct name.

We could rename this repo any time which makes one less point of confusion

We'll have to rename the Packagist package as well I imagine, which will need a bit of work?

@rmccue it's not super terrible, we'd essentially update the name in composer.json, update the name of this repo, perhaps add a "suggest" section to the composer.json and then resubmit on packagist with the new repo name and archive the old one.

For the LTS policy, I think we'd need to keep it unarchived at least until v3 is out of LTS?

Derp, yeah you're right. Not sure how well packagist copes with 2 packages driven from the same repo.

Removed the good first issue label, aliasing module names is actually gonna be quite fiddly and possibly to be avoided. I've added docs now for how to switch it off, and the longer term solution is to rename the repo & package.

In the meantime I've added some criteria to humanmade/altis-core#21 to help with this issue so there will at least be some basic validation.