Alexander Polyankin
Alexander Polyankin
Mixed FE and BE. The BE returns incorrect native form as well
We could allow you to deselect all options in the settings and simply show everything in this case in the actual widget. To confirm with design people. Or, alternatively, show...
Same issue in master. The BE doesn't return remapped values in `api/dashboard/:id/params/:param-key/search/:query` endpoint but returns in `/values`.
Empty column names are valid identifiers and we should not disallow them. You can create a table with such a column.
Still the same issue
I think that's expected behavior in a way that implicit joins for that table are not available when you explicitly joined it.
QP tries really hard to make broken queries like this work, but that's not something we want to do elsewhere. Joins aren't equal to each other, their have their own...
So for me, that's expected behavior atm - indeed the implicit join is not available after adding an explicit join, so the previous column is no longer there. There is...
Right now for me it's "working as intended"
I think the correct fix would be to detect breakages of dashboard parameters when updating queries with the dependency graph and surface such issues.