This repository has been archived by the owner on Jul 19, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 72
Change format to nested set for the dataframe #215
Merged
Merged
Changes from 1 commit
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
53e9ade
Change format to nested set for the dataframe
aocenas f16eb65
Fix test
aocenas a450005
Add comments
aocenas cdca9be
Merge branch 'main' into aocenas/change-dataframe-format
aocenas ade7ce6
Fix lint and add eslint config
aocenas c5a1e97
Merge branch 'main' into aocenas/change-dataframe-format
aocenas 5e5e9cd
Fix test
aocenas File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,23 +1,21 @@ | ||
import React from 'react'; | ||
import { DataSourcePluginOptionsEditorProps } from '@grafana/data'; | ||
import { MyDataSourceOptions } from './types'; | ||
import { DataSourceHttpSettings } from '@grafana/ui'; | ||
|
||
|
||
import { DataSourceHttpSettings } from '@grafana/ui'; | ||
|
||
interface Props extends DataSourcePluginOptionsEditorProps<MyDataSourceOptions> {} | ||
|
||
export const ConfigEditor = (props: Props) => { | ||
const { options, onOptionsChange } = props; | ||
|
||
return ( | ||
<> | ||
return ( | ||
<> | ||
<DataSourceHttpSettings | ||
defaultUrl={'http://localhost:4100'} | ||
dataSourceConfig={options} | ||
showAccessOptions={false} | ||
onChange={onOptionsChange} | ||
/> | ||
defaultUrl={'http://localhost:4100'} | ||
dataSourceConfig={options} | ||
showAccessOptions={false} | ||
onChange={onOptionsChange} | ||
/> | ||
</> | ||
); | ||
} | ||
); | ||
}; |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
this is here to reconstruct the flamebearer struct (for now), but will eventually get dropped once we swap out renderers?
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.
Yes did not think about direct transform from flamebearer to nested set format so needed the intermediate tree structure but hope to get rid of it eventually. Removing this needs change in the Fire API rather than change on the frontend though.