8a7124a15e
Follow up to #11375. When setting `filterOptions` on relationship or upload fields _that are nested within a named field_, those options won't be applied to the `Filter` component in the list view. This is because of how we key the results when resolving `filterOptions` on the server. Instead of using the field path as expected, we were using the field name, causing a failed lookup on the front-end. This also solves an issue where two fields with the same name would override each other's `filterOptions`, since field names alone are not unique. Unrelated: this PR also does some general housekeeping to e2e test helpers. --- - To see the specific tasks where the Asana app for GitHub is being used, see below: - https://app.asana.com/0/0/1211332845301583
6 lines
241 B
JavaScript
6 lines
241 B
JavaScript
export { addGroupBy } from './addGroupBy.js'
|
|
export { clearGroupBy } from './clearGroupBy.js'
|
|
export { closeGroupBy } from './closeGroupBy.js'
|
|
export { openGroupBy } from './openGroupBy.js'
|
|
export { toggleGroupBy } from './toggleGroupBy.js'
|