Now that Views is in core, this can now more than ever be called the canonic way to let admins define and display lists of content/data. Therefore, in this project's D8 branch it might be opportune to think about moving the Views integration from search_api_views
into the search_api
module itself.
Since practically all of the integration is (and will be) in separate files anyways, there'd be virtually no overhead to users who don't want to use Views to display searches. And while enabling an additional module is certainly not a high entry barrier, it's still not really necessary. (Also, every additional enabled module adds overhead.)
What other pros are there? Are there any real cons? Should we do this?
Input welcome!
Comments
Comment #1
drunken monkeyComment #2
drunken monkeyDecided and done. (Though the Views integration itself is far from finished.)