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

Many numbers have a possible 'null' value in the websocket api #1

Open
daboross opened this issue Jul 29, 2017 · 0 comments
Open

Many numbers have a possible 'null' value in the websocket api #1

daboross opened this issue Jul 29, 2017 · 0 comments

Comments

@daboross
Copy link
Owner

It's currently assumed that numbers such as nextRegenerationTime in Source, or resource numbers in terminals, are either non-existant, or 0. This simply isn't true: both of these can also be null.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@daboross