sherrardb

@abh, thanks for the feedback. leaving these open as a reminder to review during the next major push.

@youradds, we do not currently support sessions, but i am leaving this open as a reminder to review during the next major push.

indeed. depending on your perl skill level and inclination, and especially since you have a real-world use-case, you could consider putting together a pull request, and associated unit tests.

@cjavilla-stripe sorry for the delay. been tied up with some work projects. can you provide some detailed output and context for your errors. IIRC, there were some known errors related...

@abh, thanks for the feedback. leaving these open as a reminder to review during the next major push.

FTR, `Type::Tiny` is germane here because the `Kavorka` converts any `Moose::Util::TypeConstraints` used in method signatures into `Type::Tiny` objects, and therefore that is where any message about invalid parameters are generated.

unfortunately, the above does not work for `Kavorka` signature errors for TypeConstraints. and Type::Tiny doesn't currently support appending the stack trace to the emitted message. even though it is a...

``` Carp::cluck( "$e" ) if $self->debug; ```

methods used on the request side fall into this category as well. and we already have an example: ``` Placeholder: { my $return = { Net::Stripe::Resource::form_fields_for_hashref( "hashref", { level1=> {...