Merged
Conversation
The new layout does not include these tabs; their utility is redundant with the ScopeSelector dropdown in the search bar.
Randomly found this orphaned rule while in here. The consuming component was deleted in a previous commit (ef8d7ea).
Others in this component already use codeQueryBar, so...
This required a little coordination between the two components through a couple of sass variables.
This was incorrect for two reasons: * You need to interpolate the sass variable within calc * This is the same as width: auto and can be deleted
Also removes some odd spacing surrounding the text; that should be done with CSS instead.
The copy previously had a leading space; using margin is a better approach. The class that was replaced was unused.
This tweaks the pink badge to be aligned with the text on the flyout title. Also removes a now-obsolete className (code-flyout-title).
* Indents facets below the filter's title * Adjusts spacing to be more consistent, removes use of EuiSpacer NB there's a bit of a hack for the indentation itself: we use an empty, fixed-width div for the facet's icon prop.
These were introduced by some default vscode settings, which have now been resolved.
Rather than use an empty, fixed-width div as an icon, just give it some margin-left.
Contributor
|
Pinging @elastic/code |
daveyholler
suggested changes
Sep 16, 2019
| @@ -0,0 +1,3 @@ | |||
| $codeSideBarWidth: 16rem; | |||
| $codeSideBarIndent: 2rem; | |||
Contributor
Author
There was a problem hiding this comment.
@daveyholler in general: what about multipliers larger than 2.5? E.g. should the line above be 16rem or calc(#{$euiSize} * 16) or calc(#{$euiSizeXL} * 8)?
Contributor
There was a problem hiding this comment.
I'd opt for the former calc(#{$euiSize} * 16)
Contributor
💔 Build Failed |
Contributor
💔 Build Failed |
Contributor
💔 Build Failed |
These existed in the ScopeTabs component which has been deleted.
Contributor
💚 Build Succeeded |
mw-ding
approved these changes
Sep 17, 2019
Contributor
mw-ding
left a comment
There was a problem hiding this comment.
tested locally and LGTM.
Contributor
|
@daveyholler Davey, can you take a second look? |
daveyholler
approved these changes
Sep 17, 2019
* master: (33 commits) [easy] Exclude __examples__ from coverage (elastic#45556) [DOCS] Update CCR links (elastic#44012) Use unique junit report filenames again (elastic#45897) [ftr/savedObjects] add simple saved object api client to ftr s… (elastic#45856) New visualization editor Lens (elastic#36437) Sort using unix timestamp value (elastic#43162) [APM] Use POST instead of implicit GET (elastic#45903) [Canvas] Converting workpad header components to typescript and adding i18n (elastic#45274) skip flaky test (elastic#45884) set IS_PIPELINE_JOB in intake jobs (elastic#45850) [Uptime] Fix/issue 48 integration popup closes after refresh (elastic#45759) [Logs UI] Support zoom by brushing in the log rate chart (elastic#45879) [DOCS] Changes name to host (elastic#45798) [ML] Add population job wizard test (elastic#45765) [skip-ci][Maps][File upload] Geojson indexing and styling docs (elastic#41394) remove setTimeoue for state change (elastic#45853) [Graph] Restructure folders and add readme (elastic#45782) [ML] Enhance job id error message (elastic#45349) [SIEM] Do not update state component when they did unmount (elastic#45847) [i18n] sync from 7.4 latest translations (elastic#45823) ...
41683c0 to
f27d4c8
Compare
Contributor
💚 Build Succeeded |
Contributor
|
@rylnd friendly reminder on the backporting. |
Contributor
Author
On it, there were conflicts that I'm currently resolving. |
rylnd
added a commit
to rylnd/kibana
that referenced
this pull request
Sep 17, 2019
* Remove now-unused ScopeTabs component The new layout does not include these tabs; their utility is redundant with the ScopeSelector dropdown in the search bar. * Remove unused style Randomly found this orphaned rule while in here. The consuming component was deleted in a previous commit (ef8d7ea). * Use consistent block names in our BEM classes Others in this component already use codeQueryBar, so... * Move the Search bar above both the sidebar and main content * Align the search dropdown's RHS with the search sidebar This required a little coordination between the two components through a couple of sass variables. * Remove erroneous width rule This was incorrect for two reasons: * You need to interpolate the sass variable within calc * This is the same as width: auto and can be deleted * Copy: Search Filter -> Advanced Filter Also removes some odd spacing surrounding the text; that should be done with CSS instead. * Space out badge with margin, not nbsp The copy previously had a leading space; using margin is a better approach. The class that was replaced was unused. * Fix alignment of Filters flyout badge This tweaks the pink badge to be aligned with the text on the flyout title. Also removes a now-obsolete className (code-flyout-title). * Adjust layout of Search filter sidebar * Indents facets below the filter's title * Adjusts spacing to be more consistent, removes use of EuiSpacer NB there's a bit of a hack for the indentation itself: we use an empty, fixed-width div for the facet's icon prop. * Fix newline errors These were introduced by some default vscode settings, which have now been resolved. * Update snapshots following markup changes * Less hacky way of indenting facet buttons Rather than use an empty, fixed-width div as an icon, just give it some margin-left. * Swap hardcoded rem values for equivalent eui vars * One more eui var replacement * Remove unused import * Remove unused translations These existed in the ScopeTabs component which has been deleted.
rylnd
added a commit
to rylnd/kibana
that referenced
this pull request
Sep 18, 2019
* Remove now-unused ScopeTabs component The new layout does not include these tabs; their utility is redundant with the ScopeSelector dropdown in the search bar. * Remove unused style Randomly found this orphaned rule while in here. The consuming component was deleted in a previous commit (ef8d7ea). * Use consistent block names in our BEM classes Others in this component already use codeQueryBar, so... * Move the Search bar above both the sidebar and main content * Align the search dropdown's RHS with the search sidebar This required a little coordination between the two components through a couple of sass variables. * Remove erroneous width rule This was incorrect for two reasons: * You need to interpolate the sass variable within calc * This is the same as width: auto and can be deleted * Copy: Search Filter -> Advanced Filter Also removes some odd spacing surrounding the text; that should be done with CSS instead. * Space out badge with margin, not nbsp The copy previously had a leading space; using margin is a better approach. The class that was replaced was unused. * Fix alignment of Filters flyout badge This tweaks the pink badge to be aligned with the text on the flyout title. Also removes a now-obsolete className (code-flyout-title). * Adjust layout of Search filter sidebar * Indents facets below the filter's title * Adjusts spacing to be more consistent, removes use of EuiSpacer NB there's a bit of a hack for the indentation itself: we use an empty, fixed-width div for the facet's icon prop. * Fix newline errors These were introduced by some default vscode settings, which have now been resolved. * Update snapshots following markup changes * Less hacky way of indenting facet buttons Rather than use an empty, fixed-width div as an icon, just give it some margin-left. * Swap hardcoded rem values for equivalent eui vars * One more eui var replacement * Remove unused import * Remove unused translations These existed in the ScopeTabs component which has been deleted.
rylnd
added a commit
that referenced
this pull request
Sep 19, 2019
* Remove now-unused ScopeTabs component The new layout does not include these tabs; their utility is redundant with the ScopeSelector dropdown in the search bar. * Remove unused style Randomly found this orphaned rule while in here. The consuming component was deleted in a previous commit (ef8d7ea). * Use consistent block names in our BEM classes Others in this component already use codeQueryBar, so... * Move the Search bar above both the sidebar and main content * Align the search dropdown's RHS with the search sidebar This required a little coordination between the two components through a couple of sass variables. * Remove erroneous width rule This was incorrect for two reasons: * You need to interpolate the sass variable within calc * This is the same as width: auto and can be deleted * Copy: Search Filter -> Advanced Filter Also removes some odd spacing surrounding the text; that should be done with CSS instead. * Space out badge with margin, not nbsp The copy previously had a leading space; using margin is a better approach. The class that was replaced was unused. * Fix alignment of Filters flyout badge This tweaks the pink badge to be aligned with the text on the flyout title. Also removes a now-obsolete className (code-flyout-title). * Adjust layout of Search filter sidebar * Indents facets below the filter's title * Adjusts spacing to be more consistent, removes use of EuiSpacer NB there's a bit of a hack for the indentation itself: we use an empty, fixed-width div for the facet's icon prop. * Fix newline errors These were introduced by some default vscode settings, which have now been resolved. * Update snapshots following markup changes * Less hacky way of indenting facet buttons Rather than use an empty, fixed-width div as an icon, just give it some margin-left. * Swap hardcoded rem values for equivalent eui vars * One more eui var replacement * Remove unused import * Remove unused translations These existed in the ScopeTabs component which has been deleted.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Checklist
Use
strikethroughsto remove checklist items you don't feel are applicable to this PR.Documentation was added for features that require explanation or tutorialsFor maintainers
This includes a feature addition or change that requires a release note and was labeled appropriately