-
Notifications
You must be signed in to change notification settings - Fork 192
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
Checking query params raises error #164
Comments
So, this is something on server right? Do you have any fix in mind? |
I think that's okay. Since null || undefined is not what check expects for? |
It is on client. On server it works fine (passing It was working fine, but I don't remember when it popped up. Maybe after triggers release. Yeah, it is bug. I haven't solution yet. My workaround is cloning query params :). I guess it is related to #163. |
I'm confused. |
Just copy & paste I've shared code that works on client & server. That's why I'm checking on client. |
I find cause of this effect. It is because Refs: ljharb/qs#80, ljharb/qs#73 So what should we do? |
Here is error stack trace
Error line: https://github.com/meteor/meteor/blob/devel/packages/check/match.js#L278 |
I think this is a bug in Meteor. That should boy check for constructor.
|
check(FlowRouter.current().queryParams, {})
(on page with empty query string).Raises
Match error: Expected plain object
.Checking with fields (e.g.
check(FlowRouter.current().queryParams, {page: String})
) raises error too.The text was updated successfully, but these errors were encountered: