Possibility to change the name of "URI"
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 6.2k
- Forks
- 468
- PR merge metrics
- No merged PRs in 30d
Description
Using your library inside a Microsoft SharePoint project, it rendered some SharePoint functionality on a page invalid, because SharePoint seems to have some own JavaScript "URI" identifier.
Including your library resulted in JavaScript errors generated by SharePoint.
Solution for me was to download your library from the Build page and then use a text editor to replace all text occurances of "URI" with "MyOwnURI".
Later, I used "MyOwnURI" when accessing your library.
Suggestion
Maybe an option on that Build page to specify a prefix or alternative name for "URI" would be helpful.
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 at the linked Build page and trace how the downloadable library is generated and exposed under the global name "URI". Define how a prefix or alternative name should be specified there, then verify that the generated download can be accessed through the chosen name without the SharePoint conflict.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100