Support class-based components and callable signature detection #56
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR represents a big set of changes to support class-based components, as described in #53. When merged, this resolves #53 .
The
README.md
is updated to reflect these changes, all tests are updated, and there are very many new tests.For a basic description of these changes from a user's perspective, see my comments to #53 here.
There is also a new
CallableInfo
facility: a frozen dataclass that holds on to just the information we need when inspecting a callable (usinginspect.signature()
now) to understand how to invoke it. We do this (rather than holding on toinspect.Signature
instances directly) for cachability;get_callable_info(c: Callable)
sits behind an@lru_cache()
.