Re: [RFC] Module code and POD for CPAN

First and foremost: nice work! It's good that you are (a) writing this module and (b) looking to release it to CPAN. It is also in pretty good shape for a first go - well done.

I was thinking Business::Stripe::Simple as the module name - is that sensible?

It isn't crazy :-) However, since Stripe can do a great deal more than you are using it for here (according to the other CPAN Stripe modules) maybe putting something about the purpose in the name would be even better. Business::Stripe::Checkout perhaps? Or ...::WebCheckout to indicate the useragent talks to the Stripe servers directly. Of course if you are planning some later features unrelated to checkout then this becomes less useful as a name.

I will have a look through the code later as time permits since this is something I might actually have a use for.

🦛

Comment on Re: [RFC] Module code and POD for CPAN

Replies are listed 'Best First'.
Re^2: [RFC] Module code and POD for CPAN by eyepopslikeamosquito (Archbishop) on Apr 14, 2021 at 09:32 UTC
Also note that pause: On the Naming of Modules exhorts you to avoid `Simple` in module names: The terms Simple, Easy, Reduced, and Tiny are some of the worst parts of the names on CPAN. They all indicate that the module is a variation of another module, but why is that variation interesting? It's usually missing or hiding some features, less flexible than the original, and in most cases, tailored to the task the author needed. What is that task though? Making it easy for you doesn't mean it's easy for the next programmer.	[reply] [d/l]
Re^2: [RFC] Module code and POD for CPAN by Bod (Parson) on Apr 14, 2021 at 11:15 UTC
Business::Stripe::WebCheckout or ~~Net::Stripe::WebCheckout~~ are the top contenders so far Thanks hippo Update: Having read some of the material suggested by eyepopslikeamosquito, Net::Stripe::WebCheckout has been eliminated.	[reply]


laziness, impatience, and hubris
	PerlMonks