Size-related usage of resources
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 238
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Description
There is no consensus on an acceptable limit for a string to be considered large; it is not the largest possible. V8-powered browsers, Firefox, and Safari conclude different maximum string lengths. This fits into the context of this utility module and is iterable on each implemented method. Depending on every functionality and size of parameters, there's a distinct proper way of doing things.
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
The issue does not name a file or test; start by reading the utility module and reviewing each implemented method for behavior with large strings and parameters. Compare the relevant string limits across V8-powered browsers, Firefox, and Safari, then define an acceptable limit and document or test the expected behavior for each method.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, typescript
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100