Raise TypeError when unknown kwargs are provided to route() #144

jamesls · 2016-10-21T20:30:55Z

In an ideal world, I'd use the foo(*, kwarg1, kwargs2) of python3.
I'd still like to enforce that kwargs are used for any route
options, but we should validate that if you do typo an arg,
we raise an appropriate error.

In an ideal world, I'd use the foo(*, kwarg1, kwargs2) of python3. I'd still like to enforce that kwargs are used for any route options, but we should validate that if you do typo an arg, we raise an appropriate error.

Raise TypeError when unknown kwargs are provided to route()

df06deb

In an ideal world, I'd use the foo(*, kwarg1, kwargs2) of python3. I'd still like to enforce that kwargs are used for any route options, but we should validate that if you do typo an arg, we raise an appropriate error.

jamesls merged commit df06deb into aws:master Oct 24, 2016

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Raise TypeError when unknown kwargs are provided to route() #144

Raise TypeError when unknown kwargs are provided to route() #144

jamesls commented Oct 21, 2016

Raise TypeError when unknown kwargs are provided to route() #144

Raise TypeError when unknown kwargs are provided to route() #144

Conversation

jamesls commented Oct 21, 2016