Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Dashboard Parameters

See original GitHub issue

Today to have a parameter at the dashboard level, we use the global flag for parameters.

New suggested flow:

Deprecate the global flag.
When adding a new widget to the dashboard, if the query has parameters we will show them to the user and let him pick what to do with them:
1. Add the parameter to the dashboard (default option), creating a dashboard parameter.
2. Map it to existing dashboard parameter (default option, if parameter with the same name exists).
3. Give the parameter a static value.
4. (Not sure we need this:) Keep it a standalone parameter at the widget level.

Things to think about:

How to show if a widget is affected by a parameter? Maybe color code them, and show this color on the widget?

Issue Analytics

State:
Created 5 years ago
Comments:10 (4 by maintainers)

Top GitHub Comments

1reaction

arikfrcommented, Aug 5, 2018

@kravets-levko the reason it’s a dropdown is because you have multiple options (Add to dashboard, Map to existing param, use static value).

I think you can start, but @kocsmy can confirm if he wants to do another iteration on the UX/design. Also, @kocsmy I think you should update the issue description with the latest mockup/design.

0reactions

jezdezcommented, Sep 26, 2018

@kravets-levko For the record, I’ve merged #2767 which has some overlap with this.