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
This looks like a fantastic module, one that I've thought about writing for a long time. I wasn't aware of the Docopt effort, glad you can leverage it.
Is there any mode of usage that would let the code define the args itself, without doing POD lookups, and then let Dist::Zilla or some other bundling tool take the spec and insert it in the POD at dist-building time? To me that seems more compact and less action-at-a-distance.
The text was updated successfully, but these errors were encountered:
Yes, that looks right - I didn't read carefully enough to see that. Then the next piece would be to take that docstring and place it into the POD when building the dist.
Not sure if it's really a good idea or not, I just always thought of the options being defined by some mini-language in the code, then inserted into the docs at release time. Then for extra points, a zsh function that parses it for auto-completion. =)
This looks like a fantastic module, one that I've thought about writing for a long time. I wasn't aware of the Docopt effort, glad you can leverage it.
Is there any mode of usage that would let the code define the args itself, without doing POD lookups, and then let
Dist::Zilla
or some other bundling tool take the spec and insert it in the POD at dist-building time? To me that seems more compact and less action-at-a-distance.The text was updated successfully, but these errors were encountered: