indexeddb-api assumes familiarity with jQuery
Open
Nobody has claimed this yet.
accepting PR
area: indexeddb-api
good first issue
- Dominant language
- JavaScript
- Stars
- 4k
- Forks
- 1.9k
- Avg merge
- 7h 53m
- Merged PRs (30d)
- 1
Description
What information was incorrect, unhelpful, or incomplete?
The indexeddb-api example uses jQuery, which complicates the message. Well-formed tutorials/examples should focus on only one subject. Could someone refactor indexeddb-api to remove its dependence on jQuery?
What did you expect to see?
Indexeddb-api written in vanilla JS.
Do you have any supporting links, references, or citations?
No response
Do you have anything more you want to share?
This post/issue should not be construed as negative criticism. I really like these DOM examples and appreciate all the hard work the programmers do.
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 by locating the indexeddb-api example and identify where it imports or calls jQuery. Refactor that example to use vanilla JavaScript while preserving its IndexedDB behavior; done means the example no longer depends on jQuery.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, jquery
- Domain
- web-dev
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100