View/sort a user's projects by "last accessed" date
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- next.js, typescript
- Domain
- full-stack
Research direction
Start by tracing how the editor page and shard manager communicate with the Next.js app, as the issue identifies these as possible sources for access data. Then determine how project access should be collected and stored before designing the profile display and reverse last-accessed sort; done means users can view and sort their projects by last accessed date.
Written by the indexing model from the issue text.
Description
Especially if projects don't have especially meaningful names, it would be nice to see "last accessed" numbers on the user profile page — and this would be useful as a primary (reverse) sort as well.
(Other information/sort options: creation date, alphabetical order.)
Primary issue here is not display or sorting but how we collect the information and store it for display. Does the editor page do a periodic ping to the server? Does next.js get this information from the shard manager?
- Dominant language
- TypeScript
- Stars
- 10
- Forks
- 1
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 17
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing 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.
More from leanprover/lean-workbench
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
leanprover/lean-workbench#54 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
leanprover/lean-workbench#184 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 48/100
leanprover/lean-workbench#182 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 54/100
leanprover/lean-workbench#181 · 1 comment ·
Maintainers usually reply within 1 day
-
First user experience involves "Imports are out of date"Possibly taken @robsimmons claimed this 6 days ago. Openbug
leanprover/lean-workbench#180 · 2 comments · 1 assignee ·
Maintainers usually reply within 1 day
All issues in leanprover/lean-workbench
Similar issues
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
components-web-app/docs#260 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
521xueweihan/HelloGitHub#4025 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
ctrf-io/playwright-ctrf-json-reporter#117 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
voidzero-dev/void#478 ·
Maintainers usually reply within 1 day