Re: RFC: Name and/or API for module ("HTML::RewriteURLs")

I definitely think you should use the top level space URL:: because that's where you are operating. If there was HTML::URL:: that would be OK or maybe even better, but there isn't currently. URL::Transform:: does already exist though. For me, the best thing is to find like-purposed modules grouped together.

Since your module does one thing to all URLs in a document, how about URL::Transform::Base ?

While searching, I wondered if the existing URL::Transform is of any interest to you?

The way forward always starts with a minimal test.

Comment on Re: RFC: Name and/or API for module ("HTML::RewriteURLs") Select or Download Code

Replies are listed 'Best First'.
Re^2: RFC: Name and/or API for module ("HTML::RewriteURLs") by stevieb (Canon) on Jul 25, 2015 at 13:54 UTC
For me personally, I think that it should stay in the `HTML` namespace, as the primary purpose is to recreate HTML docs by simply changing URLs. When I think of `URL` namespace, I'd expect to have to use both an `HTML` parser in conjunction with something from `URL`. The `HTML::URL` suggestion is a good one though... it makes sense. Something like `HTML::URL::Localize`, `HTML::URL::Rebase` etc. I still like `HTML::LocalizeURLs` / `HTML::URLLocalize` too though ;)	[reply] [d/l] [select]
Re^3: RFC: Name and/or API for module ("HTML::RewriteURLs") by parv (Parson) on Jul 25, 2015 at 20:20 UTC
Corion, whatever name you happen to choose, would you please keep "URL" singular? Reading the name with plural version sounds horrendous to my ears.	[reply]
Re^4: RFC: Name and/or API for module ("HTML::RewriteURLs") by shmem (Chancellor) on Jul 25, 2015 at 20:43 UTC
I concur. Yes. Please. perl -le'print map{pack c,($-++?1:13)+ord}split//,ESEL'	[reply]