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

automatic migration: bump-2024 #8

Merged
merged 3 commits into from
Dec 27, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion .github/workflows/linux.yml
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,8 @@ jobs:
fail-fast: false
matrix:
cip_tag:
- "5.39"
- "5.41"
- "5.40"
- "5.38"
- "5.36"
- "5.34"
Expand Down
2 changes: 2 additions & 0 deletions .gitignore
Original file line number Diff line number Diff line change
@@ -1,2 +1,4 @@
/Perl-Critic-Plicease-*
/.build
*.old
*.orig
6 changes: 6 additions & 0 deletions .vscode/settings.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
{
"pls.perlcritic.perlcriticrc": "perlcriticrc",
"pls.inc": [
"$ROOT_PATH/lib"
]
}
8 changes: 8 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,14 @@ case basis.

This is a slight remix on the prohibit leading zeros policy with some helpful exceptions.

- [Perl::Critic::Policy::Plicease::ProhibitSignaturesAndAtUnderscore](https://metacpan.org/pod/Perl::Critic::Policy::Plicease::ProhibitSignaturesAndAtUnderscore)

Prohibit the use of `@_` in subroutine using signatures

- [Perl::Critic::Policy::Plicease::ProhibitSpecificModules](https://metacpan.org/pod/Perl::Critic::Policy::Plicease::ProhibitSpecificModules)

Prohibit the use of specific modules or pragmas

- [Plicease::ProhibitUnicodeDigitInRegexp](https://metacpan.org/pod/Perl::Critic::Policy::Plicease::ProhibitUnicodeDigitInRegexp)

Prohibit `\d` (match any digit) in regular expressions without the `/a` or `/u` modifier.
Expand Down
1 change: 1 addition & 0 deletions author.yml
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,7 @@ pod_spelling_system:
- MITHALDU
- Walde
- wchristian
- Skyttä

# ug macos
- Sawa
Expand Down
2 changes: 1 addition & 1 deletion dist.ini
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ copyright_year = 2019-2024
version = 0.07

[@Author::Plicease]
:version = 2.69
:version = 2.79
release_tests = 1
installer = Author::Plicease::MakeMaker
test2_v0 = 1
Expand Down
8 changes: 8 additions & 0 deletions lib/Perl/Critic/Plicease.pm
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,14 @@ case basis.

This is a slight remix on the prohibit leading zeros policy with some helpful exceptions.

=item L<Perl::Critic::Policy::Plicease::ProhibitSignaturesAndAtUnderscore>

Prohibit the use of C<@_> in subroutine using signatures

=item L<Perl::Critic::Policy::Plicease::ProhibitSpecificModules>

Prohibit the use of specific modules or pragmas

=item L<Plicease::ProhibitUnicodeDigitInRegexp|Perl::Critic::Policy::Plicease::ProhibitUnicodeDigitInRegexp>

Prohibit C<\d> (match any digit) in regular expressions without the C</a> or C</u> modifier.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -30,14 +30,16 @@ None.
This policy can be configured to recognize additional modules as enabling the signatures feature, by
putting an entry in a .perlcriticrc file like this:

[Community::Prototypes]
signature_enablers = Plicease::ProhibitSignaturesAndAtUnderscore
[Plicease::ProhibitSignaturesAndAtUnderscore]
signature_enablers = Foo::Bar

=head1 CAVEATS

This module assumes that "prototypes" detected in a source file that has signatures enabled are actually
subroutine signatures. This is because through static analysis alone it is not possible to determine if
a "prototype" is really a prototype and not a signature. There thus may be false negatives/positives.
For older versions of L<PPI> (newer version is yet unreleased as of this writing), this module assumes
that "prototypes" detected in a source file that has signatures enabled are actually subroutine signatures.
This is because through static analysis alone it is not possible to determine if a "prototype" is really a
prototype and not a signature. There thus may be false negatives/positives. Future versions of this module
will require a L<PPI> with better signature detection.

=cut

Expand Down
Loading