Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix compatibility with very old and very new versions of Perl #37

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

johannessen
Copy link
Collaborator

  • Rest::Neo4p declares Perl v5.10.1 as the minimum required version. But the tests actually tend to fail on versions earlier than v5.14.

  • Rest::Neo4p uses the smartmatch feature, which issues warnings on Perl v5.38 and v5.40. (#35)

  • Rest::Neo4p declares several dependencies on modules that are outdated and have better drop-in alternatives, or modules that aren’t actually used at all. This can cause unnecessary problems if those other modules don’t install cleanly for whatever reason.

These changes should make REST::Neo4p work well on all Perl versions from v5.10.1 through v5.40 and beyond.

@johannessen johannessen requested a review from majensen December 11, 2024 12:39
@johannessen johannessen force-pushed the compat-perl branch 2 times, most recently from cde8c67 to 1004584 Compare December 12, 2024 00:51
REST::Neo4p 0.4000+ requires HTTP::Tiny, which was first released with Perl v5.13.9. This change adds it to the required modules for compatibility with earlier versions of Perl.

Mojo::Exception was only used in a single test, and that test is currently skipped by default. So there's currently no reason to force users to install Mojolicious.
JSON::XS has been failing to install on blead Perl for half a year (v5.41). It doesn't seem like a good idea to depend upon it.

JSON::MaybeXS is a modern replacement for JSON.pm. It can use JSON::XS and JSON::PP when available, but actually prefers Cpanel::JSON::XS, which is a long-proven and well-maintained fork of JSON::XS.

JSON::MaybeXS was already an indirect prerequisite to REST::Neo4p because Neo4j::Driver depends upon it. JSON::ize did, too; but although JSON::ize was a declared prerequisite, it's actually unused in REST::Neo4p.
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