Use Type::Tiny for the individual tests/actions?
Open
enhancement
- Dominant language
- Perl
- Stars
- 4
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
This is a speculative one. I don't know if this would be a good idea. However, I am intrigued by the idea of being able to use Type::Tiny's inlining system.
Ref: https://metacpan.org/pod/Type::Tiny
Contributor guide
Research direction
The issue names no files, tests, or entry points; begin by reviewing the repository's individual tests and actions alongside the Type::Tiny documentation. Determine whether Type::Tiny's inlining system fits those components, then define a concrete scope and acceptance criteria before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, perl
- Domain
- cli, search, tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100