When setting custom stdin it probably should not allow perl mimetype
Open
Nobody has claimed this yet.
whateverable
- Dominant language
- Raku
- Stars
- 19
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
This line is used for both fetching the code and data for stdin:
if not $response.content-type.contains(any(‘text/plain’, ‘perl’)) {
text/plain I understand, but perl is not related in this case.
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 locating the custom-stdin handling that uses the shown response.content-type check, then trace how the same condition serves code fetching and stdin data. Confirm the intended MIME types for stdin and verify that the check no longer permits the unrelated perl type without breaking code retrieval.
Written by the indexing model from the issue text.
Assessment
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100