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

Define situations that should throw errors #77

Open
trajanmcgill opened this issue Jan 18, 2020 · 1 comment
Open

Define situations that should throw errors #77

trajanmcgill opened this issue Jan 18, 2020 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@trajanmcgill
Copy link
Owner

Ease of use would be enhanced if clear mistakes are caught and descriptive errors thrown, rather than leaving a developer with buggy code wondering whether Concert.js is not working, or his/her own code is not working, and why. For instance, trying to add animation of a target feature that overlaps with another animation segment transforming the same target feature will never work. (Although perhaps some future capacity for modifying existing animation sequences could imaginably be added.)

@trajanmcgill trajanmcgill added the enhancement New feature or request label Jan 18, 2020
@trajanmcgill trajanmcgill self-assigned this Jan 18, 2020
@trajanmcgill
Copy link
Owner Author

Another case is trying to add keyframes where the number of times specified is not the same as the number of values specified.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant