be carefull with **kwargs call

[samsja]

Context

we need to be carefull when using **kwargs in a function signature.

We should always raised an expectation when too many kwargs are passed.

Example:

if I define def f(hello='hello', **kwargs) but I call the function with f(heello='hey') it will not be called at runtime and it the typo will create confusion.

We should avoid this in a systematic manner maybe with a decorator

Context

• think how to solve this problem in a general way
• go over each **kwargs usage and verify that we handle it proprely

[JoanFM]

I do not understand this issue, this is a common Python problem, I do not think we can fix it, and it would be an overkill handling this

[samsja]

Well we can def'ly fixed it. I actually think this is one of the major blocker of Jina this kwargs things since we use it everywhere.

To me if we don't tackle this from the start we create a lot of pain for users. The whole pydantic / FastAPI idea is that we should be able to catch this kind of typo

[JoanFM]

what does FastAPI and Pydantic have to do with kwargs in methods?

[samsja]

They basically never expose kwargs in public API. And if they do it is only for special method that are tagged as behind dangerous or for internal method

[JoanFM]

But this is just what they do, it is not that it is their main value proposition