You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Sometimes classes/functions/methods are decorated with callables that modify them. It's always possible to write Griffe extensions to support those statically, and they're not that hard to write, but that still requires some development time, maybe even maintenancev.
Describe the solution you'd like
For quick reports on possible breaking changes, it would be nice to allow checking breakages with dynamic analysis.
Describe alternatives you've considered
If we implement a force_inspection option, users could run both static and dynamic analysis separately. Maybe that's a simpler alternative indeed.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Sometimes classes/functions/methods are decorated with callables that modify them. It's always possible to write Griffe extensions to support those statically, and they're not that hard to write, but that still requires some development time, maybe even maintenancev.
Describe the solution you'd like
For quick reports on possible breaking changes, it would be nice to allow checking breakages with dynamic analysis.
Describe alternatives you've considered
If we implement a
force_inspection
option, users could run both static and dynamic analysis separately. Maybe that's a simpler alternative indeed.The text was updated successfully, but these errors were encountered: