Just noticed that we’re currently not using Composer’s suggest field, but might want to point out, e.g., Facets as a possible addition.
Any reason why we shouldn’t?
And: Should we be strict or lenient regarding which packages to include? I.e., I think Facets should definitely be a recommendations – but what about Autocomplete? Or Location, Pages and Saved Searches, once they have releases? And maybe even modules with new backend plugins – mainly Solr? (While I feel people usually pick the backend they want to use first and then install the necessary module, this might well help to make them aware that there is such an option in the first place. Maybe it’s not that obvious to some users, not sure.)
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | 2996936-4--composer_suggest.patch | 530 bytes | drunken monkey |
Comments
Comment #2
drunken monkeyHere would be the minimal patch, just with Facets. (We can of course also always come back and amend this.)
Comment #3
borisson_I think this should probably also include search api solr, since it is a very popular backend replacement and autocomplete since it's a feature that can benifit a lot of implementations.
However, I'm not yet convinced that we should do this. It might seem like we're picking favorites.
Comment #4
drunken monkeyI hadn’t really thought about that, to be honest, but I still wouldn’t worry too much about that. I can’t really see anyone complaining that they want to be included, too – at least not without a good claim, in which case we might want to include them anyways.
Furthermore, I’d say the usage numbers speak for themselves. We’re not picking favorites – the users are. I don’t see this as advertising modules so they get more popular, just helping possible newbies find modules that a lot of others found helpful.
So, your two additions make perfect sense (although, as said, I’m not 100% sure about including backend modules) – but I don’t think any other modules even comes close to their usage numbers. (For instance, I also wouldn’t include Saved Searches, even once that’s stable. It’s just not popular enough.)
Lastly, I’d hesitate to include any non-stable modules – which also excludes more or less all others, as far as I’m aware.
(OK, looking through all modules I could think of, I see Pages would also be a hot candidate, once that becomes stable.)
So, I think as long as we have objective criteria and don’t appear to just play favorites, we should be fine here. But it’s a good point: I definitely don’t want to just recommend modules based on personal taste, or just because they’re maintained by me.
Comment #5
drunken monkeyOh, also, it seems a few other modules are already using this: Devel, Paragraphs – and Search API Solr. The latter seem to recommend modules that define features they support – even Location, which is in Alpha. Maybe ask Markus whether he’s had any complaints?
Comment #6
borisson_I agree with that, looks great! I talked to markus - he hasn't had any negative feedback about this yet.
Comment #8
drunken monkeyOK, great to hear. Thanks!
Committed.