Closed haarg closed 9 years ago
Actually, I was wrong about the meta-object inflation. I still think it would be better to use namespace::clean though, as it doesn't bring in the dependency on Moose.
Why not namespace::sweep?
It's like namespace::autoclean without Class::MOP. :)
I personally prefer namespace::clean as it is entirely predictable, and doesn't rely on any heuristics like ::sweep. But ::sweep would also be a reasonable choice for a Moo based class.
Bump? What the state of Moo work?
The problem was deciding the structure.
@haarg had an entire (wonderful) plan but didn't get around it. Perhaps if we all get him a beer, he'd like to continue it...? :)
Or otherwise outline the plan. I failed to remember it.
Any update on this one?
There is a rewrite design, and already a work in progress by @haarg. I hope to join him at some point, but him might still finish it before I do. He's too good, that guy. :)
Bump?
There is a beautiful complete rewrite of MetaCPAN::API. It's in branch 1.000 waiting for transition to use the new Elasticsearch.pm (instead of the deprecated ElasticSearch.pm).
The new version uses Moo indeed.
Once the new version is out, I will close this ticket. It should be soon, as we're now working with Clinton (in charge of Elasticsearch.pm/ElasticSearch.pm modules) on working out a possible bug in the module.
Great! I'm waiting it :)
This merges in the master branch, and makes a few fixes to the Moo conversion branch.
Primarily, it switches from namespace::autoclean to namespace::clean. Using namespace::autoclean will force Moose meta-objects to be inflated for everything, eliminating any real benefit from using Moo.