Might be revisited in the future because it breaks a potential use case where we can define an object with params and try to pass it to several routes, some of which might be without params. Ideally, we would want an excess property check here (that forbids every property), but it doesn't seem possible.
For now, the behavior introduced by this PR seems more valuable.
Closes #49
Might be revisited in the future because it breaks a potential use case where we can define an object with params and try to pass it to several routes, some of which might be without params. Ideally, we would want an excess property check here (that forbids every property), but it doesn't seem possible.
For now, the behavior introduced by this PR seems more valuable.