PerlDancer / PerlDancer/Dancer2
Support selective DSL keywords on import?
Nobody has claimed this yet.
- Dominant language
- Perl
- Stars
- 604
- Forks
- 288
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 5
Description
Currently you cannot pick which DSL keywords would be imported from Dancer2. This also confuses static analyzer Perl::Critic. I suggest we allow this.
We currently check for the following:
:script.:syntax,:tests: No op.:nopragmas.appname, followed by a string, representing a class.dsl, following by a string representing a class.- Anything prefixed with
!, meaning "do not import this thing".
We can verify anything else is a keyword and if so, support it being used as a filter instead. This would be simpler and much more consistent with general importing conventions.
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
The issue names no files, tests, or entry points; start by locating Dancer2's DSL import handling and the existing checks for special arguments and ! exclusions. Done means ordinary DSL keywords can be used as import filters while the listed special forms and exclusion behavior continue to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- perl
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100