You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The advanced search form component currently prepopulates inputs by matching incoming parameters (e.g., f_inclusive facet values and clause search term values) with the appropriate fields in the form. However, these values are also being displayed as plain text constraints at the top of the form, even though a user can change their values within the form. Only relevant hidden search parameters that cannot be edited directly in the form should appear within the displayed constraints.
The advanced search form component currently prepopulates inputs by matching incoming parameters (e.g., f_inclusive facet values and clause search term values) with the appropriate fields in the form. However, these values are also being displayed as plain text constraints at the top of the form, even though a user can change their values within the form. Only relevant hidden search parameters that cannot be edited directly in the form should appear within the displayed constraints.
See #3278 for more discussion on this.
The text was updated successfully, but these errors were encountered: