Covid Advanced queries: broken with new filters #530
Labels
bug
Something isn't working
Comments
fengelniederhammer
added a commit
to GenSpectrum/dashboard-components
that referenced
this issue
Feb 6, 2025
* Take the "Text input - Default" story * change the `lapisField` to "hos" (i.e. making it an invalid field) * The component will show an error, because LAPIS shows an error * change the `lapisField` to "host" (i.e. making it a valid field again) Before: It would still show an error until you click "Try again" Now: It rerenders and doesn't show an error anymore Related to GenSpectrum/dashboards#530
fengelniederhammer
added a commit
to GenSpectrum/dashboard-components
that referenced
this issue
Feb 10, 2025
) * Take the "Text input - Default" story * change the `lapisField` to "hos" (i.e. making it an invalid field) * The component will show an error, because LAPIS shows an error * change the `lapisField` to "host" (i.e. making it a valid field again) Before: It would still show an error until you click "Try again" Now: It rerenders and doesn't show an error anymore Related to GenSpectrum/dashboards#530
|
It's not clear yet how we would fix it. GenSpectrum/dashboard-components#726 already provides a mitigation. We'll discuss later and come back to this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@corneliusroemer noticed this today, it only affects the advanced queries option: the advanced queries button nolonger checks if the input is valid and appears to send it as a filter to the other filter fields - this now causes an internal error
The text was updated successfully, but these errors were encountered: