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.

Sign up for GitHub

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

Jump to bottom

Error handling #22

Open
FruitieX opened this issue Mar 19, 2015 · 1 comment
Open

Error handling #22

FruitieX opened this issue Mar 19, 2015 · 1 comment
Labels
bug core Fixed by playlist refactor

Comments

@FruitieX
Copy link
Owner

Some unexpected inputs may still dump stack traces (or even crash nodeplayer if we're unlucky?). We should really try to eliminate these by reading through code and doing proper error handling (as well as tests that cover these cases!).
@FruitieX FruitieX added this to the 0.2.0 milestone Mar 19, 2015
@FruitieX
Copy link
Owner Author

FruitieX commented Apr 2, 2015

Pay attention also to function return values. Currently somewhat inconsistent, some return true/false while others return eg. songlist/undefined.

@FruitieX FruitieX modified the milestones: 0.2.0, 0.2.5 Apr 6, 2015
@FruitieX FruitieX removed this from the 0.2.5 milestone Dec 7, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug core Fixed by playlist refactor
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@FruitieX