Support use of both Fragment Abuse plugins?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 6.2k
- Forks
- 468
- PR merge metrics
- No merged PRs in 30d
Description
After noticing that you can't select both "Fragment Abuse" plugins on the Download Builder, I started to wonder why. The URI styles obviously contradict but do the code internals?
Brief Twitter conversation with @rodneyrehm would suggest that the API accessor methods conflict for these two plugins conflict. So, I guess at least one of the two plugins APIs would have to be altered in order to support both use cases with a single build of URI.js.
I'm in a situation where I am consuming 3rd party URIs w/ "fragment query strings" but parsing 1st party SPA "fragment paths"/"URL fragments".
Does this use case apply to anyone else? Other discussion points?
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 with the Fragment Abuse plugin documentation and the Download Builder to understand the two URI styles and their intended use cases. Then inspect the conflicting API accessor methods and define how both plugins could coexist without ambiguity. Done means a single build supports both fragment query strings and fragment paths, with their behavior verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100