Skip to content
This repository has been archived by the owner on Nov 3, 2021. It is now read-only.

use the existing instance of Velocity instead of requiring a new one #39

Merged
merged 1 commit into from
Oct 21, 2015

Conversation

arush
Copy link
Contributor

@arush arush commented Oct 21, 2015

without this, velocity-react was always requiring a new instance of velocity-animate, so require('velocity-animate/velocity-ui') was attaching to the wrong instance. This finds an existing instance the correct way (the same way velocity.ui.js does it)

without this, velocity-react was always requiring a new instance of velocity-animate, so require('velocity-animate/velocity-ui') was attaching to the wrong instance. This finds an existing instance the correct way (the same way velocity.ui.js does it)
@fionawhim
Copy link
Collaborator

Makes sense. Thanks for putting this together.

fionawhim added a commit that referenced this pull request Oct 21, 2015
use the existing instance of Velocity instead of requiring a new one
@fionawhim fionawhim merged commit 23b53cb into google-fabric:master Oct 21, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants