-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[Visualize] First version of by-value visualize editor #72256
Merged
majagrubic
merged 18 commits into
elastic:master
from
majagrubic:visualize-by-value-editor
Aug 18, 2020
Merged
Changes from all commits
Commits
Show all changes
18 commits
Select commit
Hold shift + click to select a range
b4972da
First version of new by-value editor
f5061c7
Adding missing null check
8d334c0
Making typescript play nicely
6295a08
Fixing failing tests
96daa2a
Merge branch 'master' into visualize-by-value-editor
elasticmachine b63976a
Merge branch 'master' into visualize-by-value-editor
db912df
Merge branch 'master' into visualize-by-value-editor
elasticmachine 8e871ce
Applying PR comments
09a8f9b
Fixing eslint errors
a201c2a
Fix save as behavior
24c1948
Fixing HTMLElement type
d4b69dc
Passing in setOriginatingApp parameter
875be62
Redirect back to dashboard if input is missing
cc59f71
Fixing i18n error
29c6a31
Merge branch 'master' into visualize-by-value-editor
1741aae
Unlink saved search
1259c98
Merge branch 'master' into visualize-by-value-editor
228d007
Fix duplicating embeddable by reference
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
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
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
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
105 changes: 105 additions & 0 deletions
105
src/plugins/visualize/public/application/components/visualize_byvalue_editor.tsx
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 |
---|---|---|
@@ -0,0 +1,105 @@ | ||
/* | ||
* Licensed to Elasticsearch B.V. under one or more contributor | ||
* license agreements. See the NOTICE file distributed with | ||
* this work for additional information regarding copyright | ||
* ownership. Elasticsearch B.V. licenses this file to you under | ||
* the Apache License, Version 2.0 (the "License"); you may | ||
* not use this file except in compliance with the License. | ||
* You may obtain a copy of the License at | ||
* | ||
* http://www.apache.org/licenses/LICENSE-2.0 | ||
* | ||
* Unless required by applicable law or agreed to in writing, | ||
* software distributed under the License is distributed on an | ||
* "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY | ||
* KIND, either express or implied. See the License for the | ||
* specific language governing permissions and limitations | ||
* under the License. | ||
*/ | ||
|
||
import './visualize_editor.scss'; | ||
import React, { useEffect, useState } from 'react'; | ||
import { EventEmitter } from 'events'; | ||
|
||
import { VisualizeInput } from 'src/plugins/visualizations/public'; | ||
import { useKibana } from '../../../../kibana_react/public'; | ||
import { | ||
useChromeVisibility, | ||
useVisByValue, | ||
useVisualizeAppState, | ||
useEditorUpdates, | ||
useLinkedSearchUpdates, | ||
} from '../utils'; | ||
import { VisualizeServices } from '../types'; | ||
import { VisualizeEditorCommon } from './visualize_editor_common'; | ||
|
||
export const VisualizeByValueEditor = () => { | ||
const [originatingApp, setOriginatingApp] = useState<string>(); | ||
const { services } = useKibana<VisualizeServices>(); | ||
const [eventEmitter] = useState(new EventEmitter()); | ||
const [hasUnsavedChanges, setHasUnsavedChanges] = useState(true); | ||
const [embeddableId, setEmbeddableId] = useState<string>(); | ||
const [valueInput, setValueInput] = useState<VisualizeInput>(); | ||
|
||
useEffect(() => { | ||
const { originatingApp: value, embeddableId: embeddableIdValue, valueInput: valueInputValue } = | ||
services.embeddable | ||
.getStateTransfer(services.scopedHistory) | ||
.getIncomingEditorState({ keysToRemoveAfterFetch: ['id', 'embeddableId', 'valueInput'] }) || | ||
{}; | ||
setOriginatingApp(value); | ||
setValueInput(valueInputValue); | ||
setEmbeddableId(embeddableIdValue); | ||
if (!valueInputValue) { | ||
history.back(); | ||
} | ||
}, [services]); | ||
|
||
const isChromeVisible = useChromeVisibility(services.chrome); | ||
|
||
const { byValueVisInstance, visEditorRef, visEditorController } = useVisByValue( | ||
services, | ||
eventEmitter, | ||
isChromeVisible, | ||
valueInput, | ||
originatingApp | ||
); | ||
const { appState, hasUnappliedChanges } = useVisualizeAppState( | ||
services, | ||
eventEmitter, | ||
byValueVisInstance | ||
); | ||
const { isEmbeddableRendered, currentAppState } = useEditorUpdates( | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The |
||
services, | ||
eventEmitter, | ||
setHasUnsavedChanges, | ||
appState, | ||
byValueVisInstance, | ||
visEditorController | ||
); | ||
useLinkedSearchUpdates(services, eventEmitter, appState, byValueVisInstance); | ||
|
||
useEffect(() => { | ||
// clean up all registered listeners if any is left | ||
return () => { | ||
eventEmitter.removeAllListeners(); | ||
}; | ||
}, [eventEmitter]); | ||
|
||
return ( | ||
<VisualizeEditorCommon | ||
visInstance={byValueVisInstance} | ||
appState={appState} | ||
currentAppState={currentAppState} | ||
isChromeVisible={isChromeVisible} | ||
hasUnsavedChanges={hasUnsavedChanges} | ||
hasUnappliedChanges={hasUnappliedChanges} | ||
isEmbeddableRendered={isEmbeddableRendered} | ||
originatingApp={originatingApp} | ||
setOriginatingApp={setOriginatingApp} | ||
setHasUnsavedChanges={setHasUnsavedChanges} | ||
visEditorRef={visEditorRef} | ||
embeddableId={embeddableId} | ||
/> | ||
); | ||
}; |
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
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.
What if you try instead to use the same
<VisualizeEditor />
at this route, but use another effects inside when you trap into/edit_by_value
path? It seems this will help to get rid ofVisualizeEditorCommon
ccomponent and code duplications betweenVisualizeByValueEditor <---> VisualizeEditor
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.
I am not sure how? Hooks need to be run in order and they don't like branching statements. I thought having separate components was actually cleaner.