-
Notifications
You must be signed in to change notification settings - Fork 41
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
Returning a null value throws an exception #120
Comments
@michaelbpaulson can you take a look at this? |
This may be fixed by the PR for: Netflix/falcor#460 Has a similar smell [ falsey values being treated as missing paths ] |
Just looked at the strack trace - has a different root cause. Added a (pending) test for it, with the PR above, and will look into a fix. |
@michaelbpaulson Can we push this to NPM? JH
|
@jhusain Well, we really need a way to track this via change logs. When we release we just have a new version with no reasoning for why the new version is needed. But ill release it. We should strongly consider getting changelists before any more active dev is done. |
v0.2.9 pushed to github / npm. |
If you return a null value like this:
{path: ['hello'], value: null}
The Router will throw an error:
I expect this has to do with JavaScript's
typeof null == 'object'
shenanigans. I could probably fix this, just wanted to record it in case somebody can get to it before I can.The text was updated successfully, but these errors were encountered: