Problem/Motivation

A listing endpoint is served either by an entity query or by a search index, and the difference is not cosmetic: facets, relevance sorting and full-text filtering exist only in the second case. Which one applies to a bundle is a property of the site, and the scanner is the only thing that can find out.

Proposed resolution

  • When search_api is installed, record the indexes, their datasources, their indexed fields and which bundles they cover.
  • When myfacet is installed, record the facets defined against those indexes.
  • Express the result as a suggestion for the listing source of each bundle, not as a decision — it becomes a facets role the site confirms.
  • Without either module the section is simply absent and every listing plans as an entity query.

Remaining tasks

Everything.

Issue fork myrest-3620003

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

sergeydruua created an issue. See original summary.

  • sergeydruua committed 090bc3cd on 1.0.x
    Issue #3620003: Read the search indexes and the facets of the site into...
sergeydruua’s picture

Status: Active » Fixed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

sergeydruua’s picture

Status: Fixed » Closed (fixed)