WordPress / WordPress/plugin-check
library_core_files should check more than just the file name
Open
Nobody has claimed this yet.
[Team] Plugins
- Dominant language
- PHP
- Stars
- 362
- Forks
- 126
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 22
Description
I'm getting a library_core_files error for polyfill.js (.min.js and .map) in the plugin. However the polyfill is something completely different than WP's polyfill.js
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 tracing the library_core_files check and how it identifies polyfill.js, including its .min.js and .map variants. Confirm the behavior against a plugin polyfill that differs from WordPress's core file, then add coverage showing that unrelated files are not reported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100