On the Nth time of using File::Slurper and JSON::MaybeXS, I decided it would be handy to have a module which just wrapped these two things up.
It would have the reverse operation as well:
I had a quick skim of CPAN, and couldn't find a clean simple interface like this. There's YANICK's File-Serialize, but it's not quite what I'm after.
I've tried various names for the functions, such as
decode_json_from_file, and am still not sure. I picked names that mirror
File::Slurper. So suggestions for naming are welcome!
I'm working on a simple module that will provide access to a subset of CalDAV features with a high-level interface. Initially it will just provide access to todo items.
There is an existing Cal::DAV module, but it doesn't do what I want, has dependencies I don't want, and I'm planning a almost completely different interface.
I'm not sure what namespace to use:
So while I don't really like ::Simple module names, I can't think of anything better right now. Any suggestions?
Mojo::Loader is my preferred module to use for finding and loading plugins, but if you use it you have to bring along all of Mojolicious, which is not to everyone's taste.
When doing my review of modules that load other modules there was really only one other contender, Module::Find, but you typically end up using that combined with Module::Runtime or similar.
The Mojolicious team don't want to split out Mojo::Loader, so I'm proposing creating a dist that is inspired by Mojo::Loader.
Thoughts for the name:
Haven't really flushed out the details of the interface yet, as you can see.
There currently isn't an easy way to iterate over all releases on CPAN, including developer releases.
This module will run one or two queries against MetaCPAN and aggregate the results, caching them in a local file. You'll be able to specify the expiry time of the local cache, using the notation supported by Time::Duration::Parse.
This module will give you the latest release of each dist currently on CPAN. Where the latest release is a developer release, the generated index will contain the latest developer release and the latest non-developer release.
An initial release would probably have just the release iterator, since that's what I need right now.
I've got a subclass of Text::Markdown to which I've so far added just two pod-like extensions, which are CPAN related:
I imagine I might add other perl related shorthands, but I wanted these two for blogging.
Thoughts on a name for this?
This is a lightweight interface to the API for verifying an email address at http://verify-email.org. Calling it an API is a bit much (see http://verify-email.org/faq.html).
The main reason for thinking about doing a module for this is so I can get Perl listed on the API page. Yes, I'm aware of the various modules that do various forms of checking whether email addresses are active. I'll list them all in the SEE ALSO.
Validate:: namespace seems to be more about data / format validation. I like the
Email::Address:: prefix — the only thing that slightly concerns me is that this is a commercial API.
I've got an existing module on CPAN, PAUSE::Permissions, which grabs 06perms.txt, caches it locally, and gives you an interface to the data in the file.
I've created another module, PAUSE::Packages, which is a similar interface, but to 02packages.details.txt.
So I've switched over to Moo, and done the caching as a role. See also:
None of these changes have been released to CPAN yet.
As I write this I see I need to change