TiddlyWiki / TiddlyWiki/MultiWikiServer
A tiddler storage system keyed to Recipe+User
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 60
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
We need some way to store tiddlers on a per-recipe-user basis, for things like drafts and story list.
The existing format is very rigid in the way it handles the bag -> tiddler -> field relationship.
I keep thinking we need a user field in the tiddler table so we can filter tiddlers by user. It would of course be nullable.
Adding a user's drafts to a writable bag isn't a great idea because those drafts would show up in every recipe. We could restrict it to only show drafts in the writable bag. Or we could add a recipe bag in position -1 to hold user-recipe-specific tiddlers.
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 reviewing the existing bag → tiddler → field relationship described in the issue, then read the linked discussion and issue #64. Define a storage model keyed by recipe and user, including how nullable user data or a recipe-specific bag isolates drafts and story lists. Done means the approach is agreed and supports per-user, per-recipe tiddlers without exposing drafts across recipes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend, database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100