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
Some collections are defined via variant queries. In our current filter input field, the variant query is not shown anyway.
Similar to CovSpectrum, let's add a toggle or similar to the "Variant Filter" section that switches between "simple input" (the current version - pango lineage and mutations) and "advanced search" (a text field that accepts a variant query).
Do we need explanation on how to use the variant query? Where should we put it?
The text was updated successfully, but these errors were encountered:
gs-text-input does not allow to set a lapisField, which is not in the data, but this would have to be done, if one wants to use gs-text-input for the variant filter. As discussed, we will not create a (web)-component for this, but just use a simple input field. We don't need any of the special features of the gs-text-input, like a dropdown selector.
Some collections are defined via variant queries. In our current filter input field, the variant query is not shown anyway.
Similar to CovSpectrum, let's add a toggle or similar to the "Variant Filter" section that switches between "simple input" (the current version - pango lineage and mutations) and "advanced search" (a text field that accepts a variant query).
Do we need explanation on how to use the variant query? Where should we put it?
The text was updated successfully, but these errors were encountered: