Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
N
nexpie-grafana-theme
Overview
Overview
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Registry
Registry
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Kornkitt Poolsup
nexpie-grafana-theme
Commits
c180facb
Unverified
Commit
c180facb
authored
Sep 14, 2020
by
Ryan McKinley
Committed by
GitHub
Sep 14, 2020
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Chore: use visualization name in field config header (#27579)
parent
0ae534a7
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
1 additions
and
1 deletions
+1
-1
packages/grafana-data/src/panel/PanelPlugin.ts
+1
-1
No files found.
packages/grafana-data/src/panel/PanelPlugin.ts
View file @
c180facb
...
@@ -317,7 +317,7 @@ export class PanelPlugin<TOptions = any, TFieldConfigOptions extends object = an
...
@@ -317,7 +317,7 @@ export class PanelPlugin<TOptions = any, TFieldConfigOptions extends object = an
for
(
const
customProp
of
builder
.
getRegistry
().
list
())
{
for
(
const
customProp
of
builder
.
getRegistry
().
list
())
{
customProp
.
isCustom
=
true
;
customProp
.
isCustom
=
true
;
customProp
.
category
=
[
'Custom options'
].
concat
(
customProp
.
category
||
[]);
customProp
.
category
=
[
`
${
this
.
meta
.
name
}
options`
].
concat
(
customProp
.
category
||
[]);
// need to do something to make the custom items not conflict with standard ones
// need to do something to make the custom items not conflict with standard ones
// problem is id (registry index) is used as property path
// problem is id (registry index) is used as property path
// so sort of need a property path on the FieldPropertyEditorItem
// so sort of need a property path on the FieldPropertyEditorItem
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment