Re: Moose Troubles

If you're going to release this on CPAN, consider renaming it to WebService::Kayako::Staff. API in the module name is strongly discouraged: http://pause.perl.org/pause/query?ACTION=pause_namingmodules#Avoid_API_Interface_and_the_like

Comment on Re: Moose Troubles

Replies are listed 'Best First'.
Re^2: Moose Troubles by three18ti (Monk) on May 27, 2012 at 21:20 UTC
Hello, Thanks for the advice and the link. My question is this, I am writing an API to an API, there are two APIs as named by my vendor 'StaffAPI', and 'RESTAPI', what you are suggesting is I rename to 'Kayako3::Staff', and 'Kayako3::REST' ? (Here's the real question) Would you say that dropping the API from the name is more important that naming cannon between my Module and the Vendor provided API? IOW, I called it StaffAPI because I thought that would reduce confusion as it is named the same by the vendor, is this an invalid reason? My second question is about the WebService name space, is some guidance on when I should and when I should not use the WebService name space?	[reply]

Replies are listed 'Best First'.

Re^2: Moose Troubles
by three18ti (Monk) on May 27, 2012 at 21:20 UTC

Hello,
Thanks for the advice and the link.

My question is this, I am writing an API to an API, there are two APIs as named by my vendor 'StaffAPI', and 'RESTAPI', what you are suggesting is I rename to 'Kayako3::Staff', and 'Kayako3::REST' ?
(Here's the real question) Would you say that dropping the API from the name is more important that naming cannon between my Module and the Vendor provided API? IOW, I called it StaffAPI because I thought that would reduce confusion as it is named the same by the vendor, is this an invalid reason?

My second question is about the WebService name space, is some guidance on when I should and when I should not use the WebService name space?

[reply]