playcanvas / playcanvas/developer-site
Add section on CORS
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- JavaScript
- Stars
- 146
- Forks
- 72
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 33
Description
It seems that there is an endless stream of developers struggling to handle issues relating to CORS. Despite it not being a PlayCanvas specific issue, we should consider adding a User Manual section on CORS and how to deal with it.
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
No file or test is named. Start by locating the User Manual structure and existing guidance on web or networking issues, then determine where a CORS section belongs. Done means the manual explains CORS-related problems and how PlayCanvas developers can address them.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100