PerlDancer / PerlDancer/Dancer2
Add plugin logic into the command line
Open
Nobody has claimed this yet.
Enhancement
Up for grabs
- Dominant language
- Perl
- Stars
- 604
- Forks
- 288
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 5
Description
From John Stoffel:
I'd love to see expanded skeletons, or a way for Plugins to add
themselves into a skeleton so that you can more easily start
using/playing with an extension in the manner the Author of the plugin
expects it to be used.
Think of it as documentation by example, with test cases too ideally.
Now how to make this work when you have *lots* of plugins all stomping
all over each other, I don't know. It's just a thought.
I had written code that does something similar to this at the Dancer Conference. I need to find it and push a sample branch.
Contributor guide
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.
Research direction
No files, tests, or concrete command entry point are named. Start by locating the command-line plugin and skeleton logic, then look for the sample branch the issue author mentioned; the desired behavior and handling of multiple plugins need to be defined before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- perl
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100