Skip to content
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

Bug/1332 standalone menus #1333

Merged
merged 4 commits into from
May 15, 2017

Conversation

shockey
Copy link
Contributor

@shockey shockey commented May 15, 2017

Fixes #1332.

To make a long story short... we use react-dd-menu for the Topbar menus, and it leans on CSSTransitionGroup for animations. Historically that's been available as an addon in React's core, but those addons are being moved out of the core and into their own packages. However, as React's developers have noted, these addon packages need their own copy of React.

This worked while all Editor components were under one bundle, but broke when we split off the Standalone preset. The implementation of these React addons resulted in a situation in which everything except the addons were respecting the Webpack configuration to get their React from window.React.

See facebook/react#7874 for another instance of this problem.


Fixed this by pulling in the one component we were using from react-dd-menu, and swapping out the react-addons-css-transition-group package for the less finicky react-transition-group/CSSTransitionGroup drop-in replacement.

@shockey shockey merged commit aae7b42 into swagger-api:master May 15, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant