Plugin still shipping with effect: false
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 358
- Forks
- 470
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 7
Description
Hello sorry for the inconvenience, but when I first submitted my plugin in #476 I forgot to add effect: true and I did with #477, but the plugin still ships with effect: false in package.json and setting it manually fixes the cors error. So does it take a while to re-update the system with effect: true or do I need to resubmit the plugin. again sorry for the inconvenience it's my first time developing a plugin 😅
Contributor guide
No contributing guide indexed for this repository
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
Compare the plugin submission in #476 with the update in #477, then inspect the shipped package.json to confirm whether effect is still false. Determine whether the marketplace needs a resubmission or an update process, and consider the issue done when the shipped package.json contains effect: true and the CORS error is resolved.
Written by the indexing model from the issue text.
Assessment
- Domain
- release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100