So what’s new?
- Added Two more output formats:
- infile, output format, module v perl files they were Found in
- metajson, output format META.json
- Internal scanner update and why
- Finish off conversion to Type::Tiny
Food for thought, if we update our Modules, don’t we want our users to use the current version, so should we not by default do the same with others Modules. Thus we always show the current version number, regardless.
Two new output formats:
The following was conceived to provided a solution to RT76527.
midgen --format infile
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
NB: this is the only output format which displays the found version string, because it just makes sense in this instance. Many thanks to ETHER along the way.
The following is what midgen thinks your META.json might contain based upon your dist, or in this case a test dist.
midgen --format metajson
Internal Scanner update
These scanners enable midgen to identify prereqs->test->suggests from a META.json perspective.
Here is a flow chart that should help with why.
Many thanks to TOBYINK for his critique which resulted in the following taking another step forward.
Eval new scanner
Eval is not realy a new scanner, it’s just come of age with block support.
1 2 3 4 5
Support for barewords in Test::Requires scanner
Finish off conversion to Type::Tiny
Why? one, so I can have a consistent Type system regardless of Moose or Moo, two, it’s faster. The Second part of the conversion from MooX::Types::MooseLike to Type::Tiny.
So we have gone from this:
Many thanks to TOBYINK along the way.