nextcloud / nextcloud/notifications
OCC command to help users recover their notifications
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 153
- Forks
- 67
- Avg merge
- 15h 3m
- Merged PRs (30d)
- 96
Description
that may work on the web client, (I'd never seen it, or even known of its' existence until now)
but it doesn't help the desktop apps ...
I'd think it'd be helpful to have an occ command which would be able to:
- count them (all / by user / by state?)
- enumerate the oldest (all / by user / by state?)
- ack them (one/all/by user/by date? (olderthan/newerthan/range?) )
- purge them (one/all/by user/by date? (olderthan/newerthan/range?) )
I've seen slowlog entries on my host around notifications.... which is what brought this to light for me...
(datapoint of one, and I'm not confident that this was causal or just a symptom of other issues at the time.. so I don't wanna make this a focus as it could be red-herring)
Originally posted by @wolfspyre in https://github.com/nextcloud/notifications/issues/122#issuecomment-2168909473
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
The issue names no files, tests, or existing command entry point. Start by locating the project's OCC command structure and notification handling, then clarify the supported count, enumeration, acknowledgement, and purge scopes before defining completion criteria.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100