V0.3.7

[CreepySkeleton]

Closes #315

An attempt to make the hidden methods compatible with cases like that. cc @bkchr

[bkchr]

Nice, ty :)

[CreepySkeleton]

Let's postpone it until we have come up with a consensus with this

[bkchr]

In my opinion it is okay to release with these breaking changes, we will just push a fix to our code base.
However, I would vote for not hiding the functions in the StructOpt trait.

[CreepySkeleton]

release with these breaking changes

Again, none of these changes are breaking in semver sense. If you're relying on internal implementation details - you're mostly on your own.

I would vote for not hiding the functions in the StructOpt trait

Those functions are private and I'm planning to tweak them a little in #314 . I think we could move them to some sort of StrutOptMachinery trait, also hidden.

We could stabilize the augment_clap method, probably renaming it to augment_args since this is what the method does. What do you think?

[bkchr]

I just wanted to say, that you should not block because of the code I have written. I will just do the changes required and will come up later with a pr to structopt or at least an issue describing what kind of functionality I need :)

[CreepySkeleton]

It's not blocked because of the code someone have written, it's blocked on review from another maintainer, @TeXitoi . If he won't reply in 2 days I'll publish it myself.

[CreepySkeleton]

OK, I'm releasing this on my own since @TeXitoi seems to be unavailable right now, and I'm certain I can take the responsibility for this changes.

augment_clap moved to the StructOptInternal trait, also hidden. I'm not stabilizing it yet since nobody showed interest in this topic and, quite frankly, I don't feel that stabilizing anything without an approval from @TeXitoi would be fair.

[TeXitoi]

Sorry, didn't find the time to review.

[CreepySkeleton]

@TeXitoi you can make it up to me by reviewing #312 😏

[TeXitoi]

It would be approved.