in reply to CPAN module naming convention?
What name should 'PromiseHTTP' be?
Since it sounds like it extends AnyEvent::HTTP I would think that AnyEvent::HTTP::Promises would be appropriate. It also fits in with the pattern of the other more general modules AnyEvent::Promises and AnyEvent::XSPromises.
Should the 'PromiseMyApi' module be:
That's less clear-cut to me, perhaps because it isn't entirely obvious what this module actually does or is for. What is a "device" in this context? An IoT toaster or something? What is it that makes this module more useful than just working with AnyEvent::HTTP::Promises directly?
Maybe you might think about publishing AnyEvent::HTTP::Promises (which sounds like a perfectly useful module) on CPAN first on its own. That will allow people to see exactly what it does and how it works. Then with this public knowledge you can come back and show some sample code using the API/Device module and we can see how that fits in and could help choose a good name at that point. How does that sound?
HTTPEventPromises ... Devicename
These ones are not great choices - they will add entries to the top-level namespace without good reason and are therefore best avoided.
🦛
|
|---|