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
Hackable: build extensions on top of it however you like
However, after attempting to "hack" this library, I've found that this goal isn't being met satisfactorily. Many outstanding issues also seem to reflect this, a significant number caused (imo) by #53. The tight coupling between parsing, IO, and execution, in addition to a significant amount of essential API elements being non-constructable (Argument/Option/CLIEntity constructors are internal) without going through an ArgParser, make it nearly impossible to "hack" useful/unexpected behaviors on top of this library.
Can someone elaborate on the intention here? I freely admit I could be interpreting this goal incorrectly.
The text was updated successfully, but these errors were encountered:
Your documentation states:
However, after attempting to "hack" this library, I've found that this goal isn't being met satisfactorily. Many outstanding issues also seem to reflect this, a significant number caused (imo) by #53. The tight coupling between parsing, IO, and execution, in addition to a significant amount of essential API elements being non-constructable (Argument/Option/CLIEntity constructors are internal) without going through an ArgParser, make it nearly impossible to "hack" useful/unexpected behaviors on top of this library.
Can someone elaborate on the intention here? I freely admit I could be interpreting this goal incorrectly.
The text was updated successfully, but these errors were encountered: