oxalorg / oxalorg/4ever-clojure
Lazily load problem data
Nobody has claimed this yet.
- Dominant language
- Clojure
- Stars
- 271
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Description
The data in data.cljc is effectively JSON / EDN. We don't need to load all this data in the first page load, but only the problem titles. Once you navigate to a problem, you can then load the problem data and show some other solutions when the problem is solved (these solutions could be contributed through PRs). I propose to store every problem in a separate JSON file that can be fetched using an HTTP request to implement this lazy loading.
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
Start by reading data.cljc to understand how problem data is currently represented and loaded. Trace the first-page loading path and the problem navigation path. Done means the initial load includes only problem titles, while navigating to a problem fetches its full data over HTTP and supports showing additional solutions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clojure
- Domain
- frontend, performance, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100