Filter bindings

[deanhannigan]

Description

Added the ability to use bindings when filtering tables or creating views. Supports handlebars, js and js snippets!

• When browsing a table in the Data section you can now apply a number of bindings directly to a filter.
• You can incorporate a mixture of useful bindings and save them as a reusable View.
• Internal datasources utilising User field types can filter rows by app user id. The Current User bindings can be used to filter rows by the currently logged in user.
• Components in the builder can also apply filter bindings to their respective datasource settings.
• Updated UX utilising the new drawers

Binding Categories

• Current User - metadata for the currently authenticated user. If a view or filter is executed outside of a session e.g. in a public screen, the Current User bindings will not resolve.
• Date - contains a Server date binding. This will reflect the timestamp at the moment the view/filter is executed.
• Helpers - the same handlebars helpers used throughout Budibase e.g. {{ default Current User._firstName 'no user'}}

Addresses

• https://linear.app/budibase/issue/BUDI-8152/secure-access-to-my-records

Screenshots

Previously the filter type only allowed the use of static values. Now there is a second binding option.

A view created with a simple js binding to check for rows created in the last 2 weeks.

A view created with a js snippet.

A view filtering by a user column matching by the sessions current user id. This example utilises the handlebars syntax

Launchcontrol

Bindings now available when creating views, table filters or filtering builder component datasources.

[deanhannigan]

I've marked two of the tests related to Multiuser columns as !sqs. The SQS search doesn't seem to fully support them yet. The search logic does return the correct rows in the responses, but the Multiuser columns are empty causing them to appear to fail.

[samwho]

From a backend perspective, barring a couple of small questions, I'm happy with this.

Thanks so much for extending search.spec.ts, the tests for this are really good!