-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Code] Export integration components #47636
Conversation
Pinging @elastic/code (Team:Code) |
@mw-ding thoughts here? CI is currently failing due to some part of the CI/build process not liking the |
This comment has been minimized.
This comment has been minimized.
retest |
@elasticmachine merge upstream |
This comment has been minimized.
This comment has been minimized.
💔 Build Failed
|
💚 Build Succeeded
|
This separates the current CodeBlock component into two: * BareCodeBlock, which simply renders the code view without padding/margin * CodeBlock, which wraps the BareCodeBlock in an EUIPanel and allows overrides It seems like APM will want to use the former for their integration, while the latter is currently used internally by Code. It's very simple, though, and could absolutely be inlined.
This has no styling, and so a header could go right against it, it could be shown/hidden distinct from the header, etc.
Adds a 'shared' manifest that does all the reaching in; the main one just re-exports that.
This was incorrectly placed a level too high, in the plugin itself.
CodeBlockPanel = EuiPanel + CodeBlock
04acfa2
to
53d4b03
Compare
@@ -1,4 +1,4 @@ | |||
.codeContainer__root { | |||
.codeContainer__monaco { |
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.
@daveyholler @cchaos I renamed this because it was doing double duty: it applied both the monaco fixes here and also applied some layout rules in a layout file. .codeContainer__monaco
is now solely for monaco fixes, and .codeContainer__root
is for the layout stuff.
Additionally, our two uses of monaco, in our CodeBlock and EditorComponent components, both have the codeContainer__monaco
class applied internally so that consumers don't need to worry about it.
💚 Build Succeeded |
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.
LGTM. Cool, let's update the doc in the code repository and then let the APM folk know in the channel.
* Expose CodeBlockPanel component This separates the current CodeBlock component into two: * CodeBlock, which simply renders the code view without padding/margin * CodeBlockPanel which wraps the CodeBlock in an EUIPanel and allows overrides It seems like APM will want to use the former for their integration, while the latter is currently used internally by Code. It's very simple, though, and could absolutely be inlined. * Update demo page to use CodeBlock This has no styling, and so a header could go right against it, it could be shown/hidden distinct from the header, etc. * Export our current integration components from main index Adds a 'shared' manifest that does all the reaching in; the main one just re-exports that. * Move shared exports to the frontend manifest This was incorrectly placed a level too high, in the plugin itself. * Rename to better reflect relationship CodeBlockPanel = EuiPanel + CodeBlock * Distinguish monaco CSS overrides with page-specific layout
* Expose CodeBlockPanel component This separates the current CodeBlock component into two: * CodeBlock, which simply renders the code view without padding/margin * CodeBlockPanel which wraps the CodeBlock in an EUIPanel and allows overrides It seems like APM will want to use the former for their integration, while the latter is currently used internally by Code. It's very simple, though, and could absolutely be inlined. * Update demo page to use CodeBlock This has no styling, and so a header could go right against it, it could be shown/hidden distinct from the header, etc. * Export our current integration components from main index Adds a 'shared' manifest that does all the reaching in; the main one just re-exports that. * Move shared exports to the frontend manifest This was incorrectly placed a level too high, in the plugin itself. * Rename to better reflect relationship CodeBlockPanel = EuiPanel + CodeBlock * Distinguish monaco CSS overrides with page-specific layout
Summary
Addresses elastic/code#1677.
Also addresses elastic/code#1679.