(Partial) keyword argument forwarding
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.8k
- Forks
- 302
- Avg merge
- 23h
- Merged PRs (30d)
- 8
Description
Split from #1000.
I have a similar use case with Ariadne middleware functions, but with kwargs. In Ariadne, a "resolver" function takes two positional arguments and a varying number of keyword arguments that depend on the API the resolver implements. As the name implies, a middleware function sits between Ariadne and the resolver function and forwards arguments.
Ideally, I would like to type a middleware function as follows:
_P = ParamSpec("_P")
_R = TypeVar("_R")
_T = TypeVar("_T")
def foo_middleware(
resolver: Callable[Concatenate[_T, GraphQLResolveInfo, _P], _R],
obj: _T,
info: GraphQLResolveInfo,
/,
**kwargs: _P.kwargs,
) -> _R:
...
return resolver(obj, info, **kwargs)
But currently this isn't possible, because _P.args is "missing".
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the related issue #1000 and the ParamSpec/Concatenate example in this issue. Compare the desired Ariadne middleware signature with current keyword-argument forwarding behavior; done means the requested partial forwarding is supported without requiring the missing positional component, with corresponding typing behavior established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100