When a user logs out, delete non-public data from the quadstore
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 153
- Forks
- 46
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 7
Description
When a user logs out, should we not delete from the store the data which was loaded when they were logged in, which is not public?
Dat which was loaded with WAC-Allow: public=read OWTTE (including ontologies etc and public datasets) can be left.
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 names no files, tests, or entry points; first trace the logout flow and the quadstore loading and ownership paths in solid-ui. Clarify the policy for retaining public data versus removing non-public data, then define tests showing that logout removes only non-public data and leaves public data intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- authentication, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100