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
Looking at it... it seems like one should do the ast.parse trick in the PropertySignature constructor. However, I'm not sure if you want to keep using those globals in FunctionSignature? Maybe it would make more sense to have some kind of validator class for storing all of those globals?
The text was updated successfully, but these errors were encountered:
I agree, this is should be processed same way as other signatures. I consider this as a minor enchantment request (likewise #33) rather than a serious bug since it affects only modules with flawed bindings.
The library design is far from being perfect (initially was written in ~1 day as ad-hoc tool for my own use), I'm even considering complete rewrite as an option.
Therefore suggested refactoring is a plausible way.
Same problem as #33, but for properties instead!
Looking at it... it seems like one should do the
ast.parse
trick in thePropertySignature
constructor. However, I'm not sure if you want to keep using those globals in FunctionSignature? Maybe it would make more sense to have some kind of validator class for storing all of those globals?The text was updated successfully, but these errors were encountered: