Adds `Tooltip` component #501

montezume · 2019-02-01T12:47:07Z

Tooltip

Description

Tooltips display informative text when users hover over or focus on an element.

Usage

<Tooltip
  position="left"
  label="If you buy a pizza, you will also get a free ice cream :)"
>
  <button onClick={orderPizza({ freeIceCream: 'yes please' })}>Submit</button>
</Tooltip>

Working with disabled child elements

When you use a tooltip with a disabled element, you should the style pointer-events: none to the disabled element to stop it from capturing events.

<Tooltip
  position="left"
  label="You do not have permission to delete the database"
>
  <button
    disabled
    onClick={deleteDb()}
    style={{
      pointerEvents: 'none',
    }}
  >
    Delete production database
  </button>
</Tooltip>

Customizing the wrapper

The tooltip applies event listeners (onMouseOver, onMouseLeave, onFocus, and onBlur) to a wrapping component around the passed in component. By default, this wrapper is displayed with style inline-block. If you want to customize this behaviour, then you can pass in a custom wrapping element.

const Wrapper = styled.div`
  display: block;
`;

const FullWidthButton = styled.button`
  display: block;
  width: 100%;
`;

<Tooltip title="Delete" components={{ WrapperComponent: Wrapper }}>
  <FullWidthButton>Submit</FullWidthButton>
</Tooltip>;

Properties

Props	Type	Required	Values	Default	Description
`isOpen`	`bool`	-	-	-	If passed, the tooltip's open and closed states are controlled by this prop
`leaveDelay`	`number`	-	-	0	Delay (in milliseconds) between the end of the user interaction, and the closing of the tooltip
`onOpen`	`func`	-	-	-	Called when the tooltip is opened
`onClose`	`func`	-	-	-	Called after the tooltip is closed
`position`	`object`	-	`top`, `top-start`, `top-end`, `right`, `right-start`, `right-end`, `bottom`, `bottom-end`, `bottom-start`, `left`, `left-start`, `left-end`	`top`	How the tooltip is positioned relative to the child element
`horizontalConstraint`	`object`	-	`xs`, `s`, `m`, `l`, `xl`, `scale`	`scale`	Horizontal size limit of the tooltip
`children`	`node`	✅	-	-	Content rendered within the tooltip
`components`	`object`	-	`WrapperComponent`	-	If passed, the tooltip will wrap your component with this element

montezume · 2019-02-05T12:45:25Z

src/components/buttons/accessible-button/accessible-button.js

@@ -28,6 +28,7 @@ const AccessibleButton = React.forwardRef((props, ref) => (
      props.isDisabled &&
        css`
          cursor: not-allowed;
+          pointer-events: none;


otherwise it swallows up events

We should leave a comment to explain the reasons

Maybe instead more examples of uses with different elements would be useful>?

Sure, but also I mean for future references when someone looks at this code and it might not be clear what the reason for disabling pointer events is.

montezume · 2019-02-05T13:51:55Z

Percy is not playing at all nicely with the positioning library I'm using. It might not be possible to make useful VRTs for these tooltips.

tdeekens · 2019-02-05T13:37:00Z

src/components/buttons/flat-button/flat-button.js

@@ -37,9 +38,10 @@ const getTextColor = (tone, isHover = false) => {

 export const FlatButton = props => {
  const dataProps = {
-    'data-track-component': 'LinkButton',
+    'data-track-component': 'FlatButton',


tdeekens · 2019-02-05T13:37:21Z

src/components/buttons/primary-button/primary-button.js

 import Spacings from '../../spacings';
 import AccessibleButton from '../accessible-button';
 import {
  getButtonLayoutStyles,
  getButtonStyles,
 } from './primary-button.styles';

-const PrimaryButton = props => {
+const PrimaryButton = React.forwardRef((props, ref) => {


Does every component wanting to render a tooltip forward a ref?

Warning: Function components cannot be given refs. Attempts to access this ref will fail.

Yeah, good call. Should add this to the docs.

Reworked it to not need this. All it requires is that the child spreads the event listener props

tdeekens · 2019-02-05T14:06:04Z

src/components/tooltip/tooltip.js

+  horizontalConstraint: PropTypes.oneOf(['xs', 's', 'm', 'l', 'xl', 'scale'])
+    .isRequired,
+  leaveDelay: PropTypes.number.isRequired,
+  open: PropTypes.bool,


Nitpick: how is UIKit's naming convention. Is it isOpen in this case maybe?

tdeekens · 2019-02-05T14:06:33Z

src/components/tooltip/tooltip.spec.js

+        };
+      }
+    }
+);


Maybe put into a ui-kit/mocks/applyPopperMocks.js cause then it could be reused.

Yeah good call 👍

tdeekens · 2019-02-05T14:07:14Z

src/components/tooltip/tooltip.js

+    }
+  };
+
+  onRootRef = ref => {


Is this more a setRootRef? I am just trying to follow along.

tdeekens · 2019-02-05T14:08:48Z

src/components/tooltip/tooltip.js

+      ...this.props.children.props,
+    };
+
+    childrenProps.onMouseOver = this.handleEnter;


Why do we do this here and not in L117? Just onMouseLeave: this.handleLeave etc?

tdeekens · 2019-02-05T15:51:55Z

src/components/buttons/flat-button/flat-button.js

    ...filterAriaAttributes(props),
    ...filterDataAttributes(props),
+    ...filterEventAttributes(props),


Is this function exported from UI-Kit then for app level components to spread event props? I still wonder if we should rather export a

import { Tooltip } from 'ui-kit'; const Component = Tooltip.forwardProps(props => <div {...props} />

which would internally can use the filterEeventAttributes but I like the api more as the origin of the props is clear and the Tooltip gets the change to potentially spead any other props or even refs (2nd arg).

I don't really see the point of having this functionality when most people will just follow the readme and do something like

const Component = props => ( <div {...props}>Foo</div> )

This forwarding props only making sense because we are so against prop forwarding, but that's a technical decision we don't need to force on others...

emmenko

I left some comments, I'll finish reviewing this later.

emmenko · 2019-02-06T09:19:47Z

src/components/buttons/accessible-button/accessible-button.js

@@ -28,6 +28,7 @@ const AccessibleButton = React.forwardRef((props, ref) => (
      props.isDisabled &&
        css`
          cursor: not-allowed;
+          pointer-events: none;


We should leave a comment to explain the reasons

emmenko · 2019-02-06T09:22:01Z

src/components/internals/root-ref/root-ref.js

+  }
+}
+
+RootRef.propTypes = {


Nitpick: make it a static prop as well within the class?

I don't understand 🤔 Can you explain?

class RootRef extends React.Component { static propTypes = {} }

oh yeah 🤦‍♂️ . Thanks

emmenko · 2019-02-06T09:25:34Z

src/components/internals/root-ref/root-ref.js

@@ -0,0 +1,48 @@
+// inspired from https://github.com/mui-org/material-ui/blob/master/packages/material-ui/src/RootRef/RootRef.js


Can we also copy over the comments, just in case they get deleted from the source? Then we have a bit more context about the scope of this component. Thanks

Suggested change

// inspired from https://github.com/mui-org/material-ui/blob/master/packages/material-ui/src/RootRef/RootRef.js

// inspired from https://github.com/mui-org/material-ui/blob/master/packages/material-ui/src/RootRef/RootRef.js

// inspired from https://github.com/mui-org/material-ui/blob/9ecc8db8abbfb829111d3b5c0678267827984024/packages/material-ui/src/RootRef/RootRef.js#L7-L36

emmenko · 2019-02-06T09:29:38Z

src/components/tooltip/README.md

+
+#### Working with custom child elements
+
+The tooltip needs to apply DOM event listeners to its child element. If the child is a custom React element, you need to make sure that it spreads its properties to the underlying DOM element.


It would be helpful to list the DOM event listeners that we are referring to (onMouseOver, etc)

emmenko · 2019-02-06T09:30:31Z

src/components/tooltip/README.md

+      disabled
+      onClick={deleteDb()}
+      style={{
+        pointerEvents: 'none',


Should we make it clear that this needs to be set?

emmenko · 2019-02-06T09:32:54Z

src/components/tooltip/README.md

+  position="left"
+  label="You do not have permission to delete the database"
+>
+  <div style={{ cursor: 'not-allowed' }}>


How about we let the tooltip do the wrapping and the consumer can pass custom styles for this wrapper div, in case it's necessary. For example:

<Tooltip disabledWrapperStyles={{...}} disabledWrapperClassName="" > <button /> </Tooltip>

Not sure. I'd be as restrictive with UIKit as one can be. Passing classNames or styles we should maybe avoid for as long as we ever can? Maybe if needed than rather a renderWrapper or something to give full control.

Either way it's a trade off. I tried with creating a wrapper div (like we do in core Tooltip), and I found it's a lot easier for styling purposes if we don't create a wrapper div.

The styles/classname prop names are on purpose very specific to the "wrapped element", so it's not that we spread them everywhere.

I just find it a bit weird to have to wrap a div, only when in disabled state. It's going to be a "mess" from a consumer perspective

<Tooltip > {isDisabled ? ( <div style={{ cursor: 'not-allowed' }}> <MyComponent isDisabled={isDisabled} /> </div> ) : ( <MyComponent /> )} </Tooltip>

@emmenko but then we are just complaining about how the dom / html works. It's not unique to tooltips that disabled elements don't fire events 🤔

🤷‍♂️ . If we wrapped in a div, we could have like a "display: block" vs "display: inline-block" option.

Whatever works, as long as the API is simple to use.

Just leaving my humble opinion here after @montezume explained me both approaches.

I think I'm more with the mindset of Tobi, of not allowing the consumer "insert" custom styles in the component (eventhough this custom style for the wrapping div are not intended for customizing but for consistency I would say).

The reason is because allowing the user to add custom styles is not how the rest of components of UIKit works (maybe just collapsible panel which is quite old). So, for the sake of consistency (API wise) I would vote for just rely on the user to add proper children elements to the Tooltip.

If it's well documented, explaining the use case and what you should do to make it consistent in a specific scenario, for me it's more than enough as a consumer 🤷‍♂️ .

I would like to keep the API like it is for now, and if we run into problems with the migration, I'm 100% open to reworking it.

tdeekens · 2019-02-06T15:23:12Z

src/components/tooltip/tooltip.js

+    .isRequired,
+  leaveDelay: PropTypes.number.isRequired,
+  isOpen: PropTypes.bool,
+  onClose: PropTypes.func,


would a onClose: requiredIf(PropTypes.func, props => !props.isOpen) make sense?

Just to understand, by !props.isOpen, do you mean that the component is controlled by it's internal state, or it's controlled by isOpen as a prop?

Maybe it doesn't make sense true. I've just seen this elsewhere. If you pass e.g. isOpen you mean to control the component. You however can't if don't use the event handlers (which is not true in this case).

montezume · 2019-02-06T16:18:02Z

I think it makes the most sense to do a call tomorrow afternoon about this because there is some controversy surrounding the API

emmenko · 2019-02-06T13:36:50Z

src/components/tooltip/tooltip.js

+    const childrenProps = {
+      'aria-describedby': open ? this.state.id : null,
+      // for seo and accessibility, we add the tooltip's title
+      // as a native title when the title is hidden


emmenko · 2019-02-06T13:37:57Z

src/components/tooltip/tooltip.js

+    invariant(
+      !(childrenProps.disabled || childrenProps.isDisabled),
+      [
+        'ui-kit: you are providing a disabled `button` child to the Tooltip component.',


button should not be hardcoded, right?

emmenko · 2019-02-07T15:02:53Z

src/components/tooltip/tooltip.js

+      WrapperComponent: (props, propName) => {
+        if (props[propName] && !isValidElementType(props[propName])) {
+          return new Error(
+            `Invalid prop 'component' supplied to 'Route': the prop is not a valid React component`


Route 🤔

emmenko · 2019-02-07T15:05:09Z

src/components/tooltip/wrapper.js

+  children: PropTypes.node.isRequired,
+};
+
+export default Wrapper;


I think this all thing can be

export default styled.div`display: inline-block;`

montezume · 2019-02-07T16:11:21Z

Okay I updated the Tooltip to now wrap the passed in component with a div. This way, if your element is disabled, the consumer doesn't need to wrap it. By default our wrapper uses display: block, but a consumer can pass in their own custom Wrapping component like this.

import { Tooltip } from 'ui-kit';

const Button = styled.button`
   width: 100%;
   display: block;
`;

const Wrapper = styled.div`
   display: block;
`;

<Tooltip title="Hi there" components={{WrapperComponent: Wrapper}}>
   <Button>Submit</Button>
</Tooltip>

I also removed all the changes to buttons etc that added event passing

montezume · 2019-02-08T09:27:55Z

Could use some more reviews now that @emmenko's concerns have been addressed by adding the Wrapping component / cc @tdeekens

tdeekens · 2019-02-08T09:32:29Z

src/components/internals/root-ref/root-ref.spec.js

+
+class TestComponent extends React.Component {
+  state = {
+    show: this.props.show,


Nitpick: even though internal we should follow our own conventions maybe and name is isOpen or shouldShow. I don't mind too much though.

tdeekens · 2019-02-08T09:32:44Z

src/components/tooltip/tooltip.js

+      'left-end',
+    ]),
+    title: PropTypes.string.isRequired,
+    components: PropTypes.shape({


Nice and extensible!

tdeekens · 2019-02-08T09:33:24Z

src/components/tooltip/tooltip.spec.js

+    // should add the title again
+    expect(button).toHaveProperty('title', 'What kind of bear is best?');
+  });
+});


Really nice tests 💯

emmenko

Nice, I like how "simpler" it got now. If we can improve the VRT, then this is good to go.

emmenko · 2019-02-08T09:58:34Z

src/components/internals/root-ref/root-ref.js

@@ -0,0 +1,48 @@
+// inspired from https://github.com/mui-org/material-ui/blob/master/packages/material-ui/src/RootRef/RootRef.js


Suggested change

// inspired from https://github.com/mui-org/material-ui/blob/master/packages/material-ui/src/RootRef/RootRef.js

// inspired from https://github.com/mui-org/material-ui/blob/master/packages/material-ui/src/RootRef/RootRef.js

// inspired from https://github.com/mui-org/material-ui/blob/9ecc8db8abbfb829111d3b5c0678267827984024/packages/material-ui/src/RootRef/RootRef.js#L7-L36

emmenko · 2019-02-08T09:59:49Z

src/components/tooltip/README.md

+
+#### Working with disabled child elements
+
+When you use a tooltip with a disabled element, you should the style `pointer-events: none` to the disabled element to stop it from capturing events.


Suggested change

When you use a tooltip with a disabled element, you should the style `pointer-events: none` to the disabled element to stop it from capturing events.

When you use a tooltip with a disabled element, you should define the style `pointer-events: none` to the disabled element to stop it from capturing events.

src/components/tooltip/README.md

emmenko · 2019-02-08T10:01:30Z

src/components/tooltip/README.md

+
+#### Customizing the wrapper
+
+The tooltip applies event listeners (`onMouseOver`, `onMouseLeave`, `onFocus`, and `onBlur`) to a wrapping component around the passed in component. By default, this wrapper is displayed with style `inline-block`. If you want to customize this behaviour, then you can pass in a custom wrapping element.


Suggested change

The tooltip applies event listeners (`onMouseOver`, `onMouseLeave`, `onFocus`, and `onBlur`) to a wrapping component around the passed in component. By default, this wrapper is displayed with style `inline-block`. If you want to customize this behaviour, then you can pass in a custom wrapping element.

The tooltip applies event listeners (`onMouseOver`, `onMouseLeave`, `onFocus`, and `onBlur`) to a wrapping `div` component around the children element. By default, this wrapper is displayed with style `inline-block`. If you want to customize this behaviour, then you can pass in a custom element.

emmenko · 2019-02-08T10:09:36Z

src/components/tooltip/README.md

+| Props                  | Type     | Required | Values                                                                                                                                       | Default | Description                                                                                     |
+| ---------------------- | -------- | :------: | -------------------------------------------------------------------------------------------------------------------------------------------- | ------- | ----------------------------------------------------------------------------------------------- |
+| `isOpen`               | `bool`   |    -     | -                                                                                                                                            | -       | If passed, the tooltip's open and closed states are controlled by this prop                     |
+| `leaveDelay`           | `number` |    -     | -                                                                                                                                            | 0       | Delay (in milliseconds) between the end of the user interaction, and the closing of the tooltip |


Nitpick: should we maybe name this closeAfter or something similar? I feel that it's less confusing. I don't mind much though...

What about this one? 👆

src/components/tooltip/tooltip.js

emmenko · 2019-02-08T10:13:35Z

src/components/tooltip/tooltip.js

+        {open && (
+          <Popper placement={this.props.placement}>
+            {({ ref, style, placement }) => (
+              <div


We wanted to extract this into a <TooltipContent> or something, in order to run VRT on it, right?

I thought about that but it seems a bit weird since then we would need to export that, since the VRT uses the bundled ui-kit...

Hmm right...that's unfortunate 😑

emmenko · 2019-02-08T10:14:35Z

src/components/tooltip/tooltip.spec.js

+  };
+
+  static defaultProps = {
+    title: 'What kind of bear is best?',


Is this some kind of Canadian thing to say? 😅

@emmenko here

emmenko · 2019-02-08T10:15:52Z

src/components/tooltip/tooltip.visualroute.js

+export const component = () => (
+  <Suite>
+    <Spec label="Closed" omitPropsList>
+      <Tooltip title={title} eventsEnabled={false}>


Where is this prop eventsEnabled defined? 🤔

ah yeah that's a leftover from trying to get poppers to work with percy. I'll remove it.

Do you want to remove it?

emmenko · 2019-02-08T10:16:32Z

src/components/tooltip/wrapper.js

@@ -0,0 +1,5 @@
+import styled from '@emotion/styled';
+
+export default styled.div`


Nitpick: we can define this component in the tooltip.js file directly I suppose, right?

emmenko · 2019-02-08T12:31:49Z

src/components/tooltip/README.md

+      pointerEvents: 'none',
+    }}
+  >
+    Delete production database


emmenko · 2019-02-08T12:32:13Z

src/components/tooltip/tooltip.js

@@ -0,0 +1,202 @@
+// inspired from https://github.com/mui-org/material-ui/blob/9ecc8db8abbfb829111d3b5c0678267827984024/packages/material-ui/src/RootRef/RootRef.js#L7-L36


Wrong file?

emmenko · 2019-02-08T12:32:36Z

src/components/tooltip/README.md

+| Props                  | Type     | Required | Values                                                                                                                                       | Default | Description                                                                                     |
+| ---------------------- | -------- | :------: | -------------------------------------------------------------------------------------------------------------------------------------------- | ------- | ----------------------------------------------------------------------------------------------- |
+| `isOpen`               | `bool`   |    -     | -                                                                                                                                            | -       | If passed, the tooltip's open and closed states are controlled by this prop                     |
+| `leaveDelay`           | `number` |    -     | -                                                                                                                                            | 0       | Delay (in milliseconds) between the end of the user interaction, and the closing of the tooltip |


What about this one? 👆

emmenko · 2019-02-08T12:33:36Z

src/components/tooltip/tooltip.visualroute.js

+export const component = () => (
+  <Suite>
+    <Spec label="Closed" omitPropsList>
+      <Tooltip title={title} eventsEnabled={false}>


Do you want to remove it?

emmenko

💯

montezume force-pushed the ml-add-tooltip branch 2 times, most recently from 8475d49 to e27f89f Compare February 4, 2019 16:41

montezume changed the title ~~[WIP] - For deploy link - Don't review~~ Adds Tooltip component Feb 5, 2019

montezume self-assigned this Feb 5, 2019

montezume added ✨ Type: New Component labels Feb 5, 2019

montezume requested review from emmenko and tdeekens February 5, 2019 12:38

montezume commented Feb 5, 2019

View reviewed changes

montezume force-pushed the ml-add-tooltip branch from 1785255 to d8dba51 Compare February 5, 2019 13:59

tdeekens reviewed Feb 5, 2019

View reviewed changes

emmenko reviewed Feb 6, 2019

View reviewed changes

montezume force-pushed the ml-add-tooltip branch 2 times, most recently from 4578b52 to 40604f2 Compare February 6, 2019 14:23

tdeekens reviewed Feb 6, 2019

View reviewed changes

emmenko reviewed Feb 7, 2019

View reviewed changes

montezume force-pushed the ml-add-tooltip branch from 788d5a7 to 4601255 Compare February 7, 2019 16:06

tdeekens approved these changes Feb 8, 2019

View reviewed changes

emmenko reviewed Feb 8, 2019

View reviewed changes

montezume added 6 commits February 8, 2019 11:44

chore: add tooltip

b3dcea4

chore: more changes

11fefaa

chore: fixup

5d41039

chore: fixup

e67ad53

chore: use correct title

0bd51fa

chore: add padding

4dd08d9

montezume added 21 commits February 8, 2019 11:44

chore: make buttons support tooltips

4493c3d

chore: fix test

a3a71bc

chore: fixup

725ca67

chore: change vrt

8e471c2

chore: pr fixes

c64729c

chore: make tooltip work without needed to pass ref

dad2e8c

chore: pr comments

5ce5b66

chore: make radio inputs support events

250a04a

chore: add aria attributes to radio input

c713fa0

chore: update readme

d80afe7

chore: rebuild yarn lock

78b70d6

chore: fix test

ac359c7

chore: move prop types static

d542f9b

chore: allow custom wrapper components

0f54b54

chore: fixup

2d0ab27

chore: revert button changes

8dada07

chore: revert changes

7625afd

chore: remove unused code

08dc686

chore: remove unused code

8239aa1

chore: fix

d978401

chore: pr comments

b7da10d

montezume force-pushed the ml-add-tooltip branch from 29097e7 to b7da10d Compare February 8, 2019 10:57

montezume added 3 commits February 8, 2019 12:13

chore: fix

1d22e20

chore: fix

14053e4

chore: fix

7a0a9ad

emmenko reviewed Feb 8, 2019

View reviewed changes

chore: pr fixes

6fbd0ea

emmenko approved these changes Feb 8, 2019

View reviewed changes

montezume merged commit a60b6ab into master Feb 8, 2019

montezume deleted the ml-add-tooltip branch February 8, 2019 12:48

		@@ -0,0 +1,48 @@
		// inspired from https://github.com/mui-org/material-ui/blob/master/packages/material-ui/src/RootRef/RootRef.js


		#### Working with custom child elements

		The tooltip needs to apply DOM event listeners to its child element. If the child is a custom React element, you need to make sure that it spreads its properties to the underlying DOM element.


		#### Working with disabled child elements

		When you use a tooltip with a disabled element, you should the style `pointer-events: none` to the disabled element to stop it from capturing events.


		#### Customizing the wrapper

		The tooltip applies event listeners (`onMouseOver`, `onMouseLeave`, `onFocus`, and `onBlur`) to a wrapping component around the passed in component. By default, this wrapper is displayed with style `inline-block`. If you want to customize this behaviour, then you can pass in a custom wrapping element.

		@@ -0,0 +1,5 @@
		import styled from '@emotion/styled';

		export default styled.div`

		@@ -0,0 +1,202 @@
		// inspired from https://github.com/mui-org/material-ui/blob/9ecc8db8abbfb829111d3b5c0678267827984024/packages/material-ui/src/RootRef/RootRef.js#L7-L36

Adds Tooltip component #501

Adds Tooltip component #501

Conversation

montezume commented Feb 1, 2019 • edited Loading

Tooltip

Description

Usage

Working with disabled child elements

Customizing the wrapper

Properties

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

montezume commented Feb 5, 2019

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

montezume Feb 5, 2019 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

emmenko left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

montezume commented Feb 6, 2019

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

montezume commented Feb 7, 2019 • edited Loading

montezume commented Feb 8, 2019

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

emmenko left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Adds `Tooltip` component #501

Adds `Tooltip` component #501

montezume commented Feb 1, 2019 •

edited

Loading

montezume Feb 5, 2019 •

edited

Loading

montezume commented Feb 7, 2019 •

edited

Loading