-
Notifications
You must be signed in to change notification settings - Fork 11.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Scopes: Adapt for new API #87841
Scopes: Adapt for new API #87841
Conversation
❌ Failed to run Playwright plugin e2e tests. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bfmatei - the overall flow works good I think, and API adjustments are fine.
However, I have concerns about the UX, on top of the comments that I've left:
- Any change in the scope selector (selecting a scope) results in new queries. I think we may want to defer that until the scopes selector is closed.
- Would love the entire scope selector row to be clickable rather than the checkbox only.
- I miss some placeholder on the empty scope selector, currently it's just an empty input.
Would be also good if we added some tests for the tree navigation UI to make sure we are not breaking anything in the future.
public/app/features/dashboard-scene/scene/ScopesFiltersScene.tsx
Outdated
Show resolved
Hide resolved
grafana-dataRemovalsDataQueryRequest.scope/home/runner/work/grafana/grafana/base/grafana-data/dist/index.d.ts scope?: Scope | undefined; ChangesCustomVariableSupport.query/home/runner/work/grafana/grafana/pr/grafana-data/dist/index.d.ts Parameter type changed:
endTime?: number;
liveStreaming?: boolean;
hideFromInspector?: boolean;
queryGroupId?: string;
- scope?: Scope | undefined;
+ scopes?: Scope[] | undefined;
} DataSourceApi.query /home/runner/work/grafana/grafana/pr/grafana-data/dist/index.d.ts Parameter type changed:
endTime?: number;
liveStreaming?: boolean;
hideFromInspector?: boolean;
queryGroupId?: string;
- scope?: Scope | undefined;
+ scopes?: Scope[] | undefined;
}
DataSourceWithSupplementaryQueriesSupport.getDataProvider Parameter type changed:
endTime?: number;
liveStreaming?: boolean;
hideFromInspector?: boolean;
queryGroupId?: string;
- scope?: Scope | undefined;
+ scopes?: Scope[] | undefined;
}
DataSourceWithSupplementaryQueriesSupport.getSupplementaryRequest Parameter type changed:
endTime?: number;
liveStreaming?: boolean;
hideFromInspector?: boolean;
queryGroupId?: string;
- scope?: Scope | undefined;
+ scopes?: Scope[] | undefined;
}
StandardVariableSupport.query Parameter type changed:
endTime?: number;
liveStreaming?: boolean;
hideFromInspector?: boolean;
queryGroupId?: string;
- scope?: Scope | undefined;
+ scopes?: Scope[] | undefined;
}
grafana-prometheusRemovalsPrometheus.scope/home/runner/work/grafana/grafana/base/grafana-prometheus/dist/index.d.ts scope?: ScopeSpec; |
What is this feature?
The Scopes API moved to a node-based approach. This PR brings compatibility for the UI to use that client.
Why do we need this feature?
Implement Scopes?
Who is this feature for?
Which issue(s) does this PR fix?:
Special notes for your reviewer:
Screen.Recording.2024-05-16.at.11.54.39.mov
Please check that: