Creating a separate PR to show the changes needed for a separate package
New exports needed from @grafana/scenes
DataQueryExtended (renamed to SceneDataQuery)
VariableValueSelectWrapper
Some utils. / types duplicated
writeSceneLog
DeepPartial
Removed features due to move
The interoperability with contexts and EmbeddedScene had to be removed. This interoperability made it possible to use all the new hooks and components when rendering custom scene objects inside current scene apps. to restore this feature we need to create a new EmbedddeSceneWithContext component exported from @grafana/scenes-react
Current name conflicts (where @grafana/scenes exports type with same name as @grafana/scenes-react)
VizPanel
CustomVariable
To fix this name conflict we could rename the scene object variants (maybe CustomVariable => CustomVariableObject or CustomVariableDef). Or we rename the react versions. Anyway I think we can live with the name conflicts for the initial phase / versions until everything is feeling more solid.
Hook names feedback / ideas (not implemented)
useSceneQuery => useQueryRunner (or just useQuery but that will conflict with react-query)
VisualizationConfig => VizConfig
VisualizationConfigBuilders => VizConfigBuilders
📦 Published PR as canary version: 4.24.2--canary.755.9282326022.0
:sparkles: Test out this PR locally via:
```bash
npm install @grafana/scenes-react@4.24.2--canary.755.9282326022.0
npm install @grafana/scenes@4.24.2--canary.755.9282326022.0
# or
yarn add @grafana/scenes-react@4.24.2--canary.755.9282326022.0
yarn add @grafana/scenes@4.24.2--canary.755.9282326022.0
```
PR Base: https://github.com/grafana/scenes/pull/734 (Main Scenes React PR)
Creating a separate PR to show the changes needed for a separate package
New exports needed from @grafana/scenes
Some utils. / types duplicated
Removed features due to move
@grafana/scenes-reactCurrent name conflicts (where @grafana/scenes exports type with same name as @grafana/scenes-react)
To fix this name conflict we could rename the scene object variants (maybe CustomVariable => CustomVariableObject or CustomVariableDef). Or we rename the react versions. Anyway I think we can live with the name conflicts for the initial phase / versions until everything is feeling more solid.
Hook names feedback / ideas (not implemented)
📦 Published PR as canary version:
4.24.2--canary.755.9282326022.0:sparkles: Test out this PR locally via: ```bash npm install @grafana/scenes-react@4.24.2--canary.755.9282326022.0 npm install @grafana/scenes@4.24.2--canary.755.9282326022.0 # or yarn add @grafana/scenes-react@4.24.2--canary.755.9282326022.0 yarn add @grafana/scenes@4.24.2--canary.755.9282326022.0 ```