Introduce Perl::Critic Policy Plicease::ProhibitArrayAssignAref
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- perl
- Domain
- developer-experience
Research direction
The issue names no files. Start with the linked Perl::Critic policy page to see what it flags, then find where this project configures its existing Perl::Critic policies. The issue leaves open whether to add the policy at all, so confirm that decision in the thread before editing. Done means the policy is either enabled in that configuration with the code checks passing, or the issue is closed with a reason.
Written by the indexing model from the issue text.
Description
It might be worth checking whether we want to add the policy
[1]Plicease::ProhibitArrayAssignAref to the CodePolicy.
[1] https://metacpan.org/pod/Perl::Critic::Policy::Plicease::ProhibitArrayAssignAref
- Dominant language
- Perl
- Stars
- 4
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from RotherOSS/codepolicy
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
RotherOSS/codepolicy#152 ·
-
question
Difficulty 3/5 1-2 days Newbie friendliness 68/100
RotherOSS/codepolicy#151 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
RotherOSS/codepolicy#150 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
RotherOSS/codepolicy#149 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 58/100
RotherOSS/codepolicy#148 ·
All issues in RotherOSS/codepolicy
Similar issues
-
"Chia" category expects a single and specific ingredient but doesn't recognize "Salvia Hispanica"Open
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
openfoodfacts/openfoodfacts-server#15362 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
RotherOSS/servicecatalog#30 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100