Perl-Toolchain-Gang / Perl-Toolchain-Gang/Module-Metadata
test/fix: handling of =encoding directives when extracting pod
Open
Nobody has claimed this yet.
- Dominant language
- Perl
- Stars
- 8
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
(to be addressed after the more general problem of handling encodings when parsing modules)
Ensure that extracted pod is also properly decoded. see https://github.com/Perl-Toolchain-Gang/Module-Build/pull/57
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
Start by reading the module-parsing and POD-extraction entry points, with the linked Module-Build pull request as context. First account for the broader encoding-handling problem, then verify that extracted POD is decoded correctly for files containing =encoding directives.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- perl
- Domain
- documentation
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100