scenes
Build Grafana dashboards directly in your Grafana app plugins.
APACHE-2.0 License
Bot releases are visible (Hide)
Published by grafanabot 8 months ago
Published by grafanabot 8 months ago
🚀 Enhancement
-
@grafana/scenes- AdHocFilters: Auto focus value when key is selected #614 (@torkelo @darrenjaneczek)
🐛 Bug Fix
-
@grafana/scenes- feat: allow label for adhoc filter add button #619 (@darrenjaneczek)
- fix: adhoc filter placeholder to "Select value" #620 (@darrenjaneczek)
Authors: 2
- Darren Janeczek (@darrenjaneczek)
- Torkel Ödegaard (@torkelo)
Published by grafanabot 8 months ago
🚀 Enhancement
-
@grafana/scenes
🐛 Bug Fix
Authors: 2
Published by grafanabot 8 months ago
🚀 Enhancement
-
@grafana/scenes- Update grafana peer dependencies #570 (@leventebalogh @dprokop)
Authors: 2
- Dominik Prokop (@dprokop)
- Levente Balogh (@leventebalogh)
Published by grafanabot 8 months ago
Release Notes
VariableDependencyConfig: Support * to extract dependencies from every state path (#599)
Possible breaking change: VariableDependencyConfig default behavior
-
Previously: Using
VariableDependencyConfigwithout options scanned the entire state. -
Now: Default behavior requires an explicit wildcard (
*) to scan the whole state. This prevents unintended dependency resolution.
Impact: If you intentionally scanned the entire state, use statePaths: ['*']. Otherwise, specify desired statePaths or variableNames.
Example:
class TestObj extends SceneObjectBase<TestState> {
public constructor() {
super({
query: 'query with ${queryVarA} ${queryVarB}',
otherProp: 'string with ${otherPropA}',
nested: {
query: 'nested object with ${nestedVarA}',
},
});
}
}
it('Should be able to extract dependencies from all state', () => {
const sceneObj = new TestObj();
- const deps = new VariableDependencyConfig(sceneObj, {});
+ const deps = new VariableDependencyConfig(sceneObj, { statePaths: ['*'] });
expect(deps.getNames()).toEqual(new Set(['queryVarA', 'queryVarB', 'nestedVarA', 'otherPropA']));
});
This mproves performance and avoids unexpected dependency resolution.
🚀 Enhancement
-
@grafana/scenes- VariableDependencyConfig: Support
*to extract dependencies from every state path #599 (@ivanortegaalba)
- VariableDependencyConfig: Support
🐛 Bug Fix
-
@grafana/scenes- Fix typo in docstring #601 (@oscarkilhed)
- VariableDependencyConfig can extract variables from circular structures #597 (@ivanortegaalba)
Authors: 2
- Ivan Ortega Alba (@ivanortegaalba)
- Oscar Kilhed (@oscarkilhed)
Published by grafanabot 8 months ago
Release Notes
Variables: Clear current value when no options are returned (#595)
All variables that extend from MultValueVariable (Query, DataSource, Custom) now clear the current value if no options / values are returned by query, clears to empty string or array depending on multi or not.
🚀 Enhancement
Authors: 1
- Torkel Ödegaard (@torkelo)
Published by grafanabot 8 months ago
🐛 Bug Fix
-
@grafana/scenes- VariableDependencyConfig: do not scan state if
variableNamesis defined #598 (@ivanortegaalba)
- VariableDependencyConfig: do not scan state if
Authors: 1
- Ivan Ortega Alba (@ivanortegaalba)
Published by grafanabot 8 months ago
🐛 Bug Fix
-
@grafana/scenes- AdHocFiltersVariable: Allow setting expression builder function #582 (@adrapereira)
Authors: 1
- Andre Pereira (@adrapereira)
Published by grafanabot 8 months ago
Release Notes
AdHocFiltersSet/Variable: Unify both objects as a scene variable (breaking change) (#586)
AdHocFilterSet is now removed from the library. AdHocFiltersVariable can now be used in both modes (auto and manual).
To migrate replace AdHocFilterSet with AdHocFiltersVariable , the applyMode defaults to auto which is the new renamed value that was previously same-datasource. Instead of adding this directly to a controls array add it to the variables array of a SceneVariableSet. It will then be rendered along with other variables via the VariableValueSelectors controls component. If you want to render ad hoc filters separately you can set hide: VariableHide.hideVariable so that the filters are not rendered by VariableValueSelectors and use the new component VariableValueControl that can render a specific variable.
AdHocFiltersVariable.create is also removed as this separate factory function is no longer needed. If you where using AdHocFiltersVariable.create then switch to the normal constructor but be sure to pass in applyMode: 'manual' when you create it to preserve the same behavior as before.
💥 Breaking Change
-
@grafana/scenes- AdHocFiltersSet/Variable: Unify both objects as a scene variable (breaking change) #586 (@torkelo @ivanortegaalba @dprokop)
Authors: 3
- Dominik Prokop (@dprokop)
- Ivan Ortega Alba (@ivanortegaalba)
- Torkel Ödegaard (@torkelo)
Published by grafanabot 9 months ago