-
Notifications
You must be signed in to change notification settings - Fork 363
Conversation
Travis automatic deployment: Storybook book automatic deployment: |
Travis automatic deployment: Storybook book automatic deployment: |
Travis automatic deployment: Storybook book automatic deployment: |
Travis automatic deployment: Storybook book automatic deployment: |
Travis automatic deployment: Storybook book automatic deployment: |
Travis automatic deployment: Storybook book automatic deployment: |
Travis automatic deployment: Storybook book automatic deployment: |
1 similar comment
Travis automatic deployment: Storybook book automatic deployment: |
…r after 300ms after closing so user doesn\'t see the changes
Travis automatic deployment: Storybook book automatic deployment: |
Travis automatic deployment: Storybook book automatic deployment: |
Travis automatic deployment: Storybook book automatic deployment: |
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.
Looks good to me now. 👍
Travis automatic deployment: Storybook book automatic deployment: |
This PR:
react/state-in-constructor
because of an update in airbnb config, we didn't define state in constructor previously and I don't see any reason to do that.--runInBand
)SafeList
route andFooter
componentaddSafe
actions. Previously we had a default exported action which would accept the raw data and create safe instance record, and also exported an action which would just take the safe record. Default one was used only during safe creation, so I changed the creation a little bit and made action which would take the safe record defaultwaitForElement
instead ofsleep
function