Currently, ExternalEntities pass everything on EntityQueryCondition as simple REST query parameter, the operator of the EntityQueryConditon is missing, this causes certain basic functionalities fail to function, like the tracker of the SearchAPI index (requires id > LAST_ID on EntityQuery) and also the EntityReference autocompolete (requires title CONTAINS STRING).

Attached patch provides a sub-module that adds two Views Argument (id, title) that can translate the 'operator' and 'value' passed as query parameters to a SQL where expression, that the above mentioned basic functionalities could work.

CommentFileSizeAuthor
#3 3074517-3-Allows-REST-View-Display-to-be-consumed-by-External-.patch8.23 KBweynhamz

Comments

weynhamz created an issue. See original summary.

weynhamz’s picture

weynhamz
Location Ningbo
commented
Issue summary: View changes
weynhamz’s picture

weynhamz
Location Ningbo
commented
StatusFileSize
new 3074517-3-Allows-REST-View-Display-to-be-consumed-by-External-.patch8.23 KB
clemens.tolboom’s picture

clemens.tolboom
Primary language Dutch
Location Groningen, 🇳🇱/🇪🇺
commented
Status: Active » Needs review
frob’s picture

frob
Primary language English
commented

So we are clear on how to test this. This patch needs to be installed on the source and target Drupal sites. The source being the site housing the views and the target being the site that consumes the views with External Entity.

Is there any setup required on the view that uses this patch?