[Maps] More compressed forms

[cchaos]

Layer Settings

Source Settings

Vector styles

Question

I have hard-coded the px to the range labels. However, it seems it would be better to add another item to the shapes that controls the unit like:

export const staticSizeShape = PropTypes.shape({
  size: PropTypes.number.isRequired,
  unit: PropTypes.string,
});

When I tried this, however, it got really complicated. Mainly the question is, will it always be in pixels and therefore the hardcoded labels are ok, or can a dev help us expand these shapes?

Go To and Draw popovers

Checklist

Use strikethroughs to remove checklist items you don't feel are applicable to this PR.

• This was checked for cross-browser compatibility, including a check against IE11
• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• [ ] Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios
• [ ] This was checked for keyboard-only and screenreader accessibility

[elasticmachine]

Pinging @elastic/kibana-gis

[elasticmachine]

💔 Build Failed

• continuous-integration/kibana-ci/pull-request

[elasticmachine]

💔 Build Failed

• continuous-integration/kibana-ci/pull-request

[elasticmachine]

💔 Build Failed

• continuous-integration/kibana-ci/pull-request

[elasticmachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request

[nreese]

will it always be in pixels and therefore the hardcoded labels are ok, or can a dev help us expand these shapes?

Pixels should be fine. We can always refactor if that changes in the future

[nreese]

Looks great. Really like the labels to the left of the inputs and the condensed range sliders

lgtm
code review, tested in chrome

[snide]

@nreese Did you mean to mark that as approved? If so I'll just go ahead and merge/backport this since caroline is now on vacation.