Skip to content

CHI/Test.pm: Replace manual import stuff with Import::Into#18

Open
kentfredric wants to merge 2 commits into
jonswar:masterfrom
kentfredric:master
Open

CHI/Test.pm: Replace manual import stuff with Import::Into#18
kentfredric wants to merge 2 commits into
jonswar:masterfrom
kentfredric:master

Conversation

@kentfredric

Copy link
Copy Markdown

This is partially motivated by the fact Test::More is changing its
exporter.

CHI Test exposes this fact presently due to reaching into exporter internals,
causing a breakage when they cease to exist. ( Test-More/test-more#472 )

This change changes import syntax to use defined public import API to
perform imports.

And I figure that's less-ugly.

I'm not 100% certain I've done the translation correct, but CHI' passes its own tests like this.

This is partially motivated by the fact Test::More is changing its
exporter.

CHI Test exposes this fact presently due to reaching into exporter internals,
causing a breakage when they cease to exist.

This change changes import syntax to use defined public import API to
perform imports.
Unfortunately, Phase order happens as such:

- Add Files.
- Remove Files
- Munge Files
- Finalise Installer

https://metacpan.org/source/RJBS/Dist-Zilla-5.023/lib/Dist/Zilla/Dist/Builder.pm#L317

Which means without this patch, it does:

  GatherDir  ( Imports Makefile.PL from disk )
  MakeMaker  ( Injects a templated Makefile.PL )
  PruneFiles ( Removes both of the above )
  MakeMaker  ( Attempts to munge previously injected Makefile.PL and
      bails when it doesn't exist )

This patch resolves that by removing the problem file before it even
gets added to dzil, eliminating conflict.
@kentfredric

Copy link
Copy Markdown
Author

Seems the contributors readme is a bit out of date and you've got tidyall stuff. However, the tidyall stuff doesn't appear to work, and its perltidy settings seem to be completely ignored.

I've manually run perltidy on the code I submittied with the params from tidyall, and I hope the result is adequate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant