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

Avoid excessively connecting configuration properties in interactions #110

Open
jverkoey opened this issue Apr 20, 2017 · 0 comments
Open

Comments

@jverkoey
Copy link
Contributor

Some interactions connect properties to sub-interactions or other values, e.g. ArcMove's: runtime.connect(arcMove(from: from, to: to), to: tween.path). This only needs to be done once.

Closure of this task involves auditing our interactions for any runtime.connect invocations and ensuring that if they're connecting sub-interactions together that we're only doing so once.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant