As the module connects with Stripe, it is only ever going to be used in a CGI environment.

Well, not that many perl devs are using CGI anymore. Is the module not appropriate for Catalyst, Dancer, or Mojo environments?

In general, I'm in the "code that fails should die and devs should try{}catch{}" camp, with the exception that external inputs to a program should be validated in a way that doesn't involve try/catch so that remote people don't have the ability to trigger __DIE__ handlers on demand.

But also, continuing my recent Public Service Announcement about the insecurity of HTTP::Tiny, you should add verify_TLS to the HTTP::Tiny constructor before connecting to stripe API.

In reply to Re: Error handling in a module by NERDVANA
in thread Error handling in a module by Bod

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.