A tiddler storage system keyed to Recipe+User
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- typescript
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.
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.
- Dominant language
- TypeScript
- Stars
- 60
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the 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 TiddlyWiki/MultiWikiServer
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
TiddlyWiki/MultiWikiServer#140 · 4 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
TiddlyWiki/MultiWikiServer#139 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
TiddlyWiki/MultiWikiServer#138 ·
-
User creation fails with 500 error when email field is left blank - missing frontend validationOpen
Difficulty 4/5 3-5 days Newbie friendliness 48/100
TiddlyWiki/MultiWikiServer#136 · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
TiddlyWiki/MultiWikiServer#135 · 1 comment ·
All issues in TiddlyWiki/MultiWikiServer
Similar issues
-
chore v2
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
modelcontextprotocol/servers#5115 ·
Maintainers usually reply within 1 day
-
beginner bug good first issue
Difficulty 1/5 Under an hour Newbie friendliness 85/100
philaconvalley/website#168 ·
Maintainers usually reply within 1 day
-
bug frontend good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
oss-slu/lrda_mobile#294 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
hatchet-dev/hatchet#5179 ·
Maintainers usually reply within 1 day