Skip to content

Conversation

@stefanhaerter
Copy link
Contributor

closes #3186
replaces #3187

If the current issue is solved, the reference dynamic fields are no
longer prohibited from being used as targets for lens dynamic fields.
The check for reference filters took priority over the lens param
entirely, which the commit changed.

Also, the lens param needs to precede the check for reference filter
content in case that we end up there without reference filters
configured.
In case that a lens field points to a reference field, the reference
search module needs to take an extra step in looking up the target of
lens fields.
In case that the target of a lens field has the behavior
SetsDynamicContent, a call to GetFieldState() of the respective backend
is necessary to get the content.
The JS needs to be able to handle lenses on autocomplete reference
fields as well as lenses to dropdown reference fields.
Copy link
Contributor

@chzauleck chzauleck left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Regarding the changes in Core.Ajax.js:
I would suggest adding a comment when using a regular expression that gives an idea about what we're looking for there in human readable form. (no expectation to go into detail, just makes reading the code easier to have a rough idea imo)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants