Dataviews: "elements" property of field items should be a subproperty of "filterBy"

[juanmaguitar]

What problem does this address?

The elements property and the filterBy property of Dataviews are tightly coupled. In fact, filters are enabled by a field just by passing a proper array of objects to the elements property even when filterBy is empty. From a Developer Experience point of view, I think this is a bit confusing.

What is your proposed solution?

I think it makes more sense for the elements property to be a sub-property of filterBy so it's more naturally understandable that:

• Filters by a field are "enabled" when the property elements property of filterBy, receives an array of value-label objects
• Optionally, we can also define operators and isPrimary values

In the meantime, I opened #64633 to clarify this from the docs

cc: @oandregal

[oandregal]

That's something we considered at the beginning but decided against. The reason for being a standalone property is that it's shared by some features: filtering, but also editing. In the DataForm storybook there's an example that shows how elements power a radio or select control for fields.

[juanmaguitar]

I see! Thanks for the clarification @oandregal
That makes sense. I'll close this issue then.

[oandregal]

Coincidentally, there's this conversation in which we're discussing adding support for having different elements in filter & edit. 😅