is it finally time to have a 'view' collection, for routines? #121
Labels
No labels
bug
documentation
duplicate
enhancement
feature idea
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
davenh99/progressa#121
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
for the routineslist summary page, it shoud have title, desc, summary of exercises.
need something similar for a session, summary of exercises (to be more readable than the fat list)
if not the view collection, tack summary on in custom route.
begin thinking about doing 'computed' fields this way, with a custom route, and make a plugin for it, that talks to auto-gen types. makethem readonly in typescript (sending these to backend will silently fail as of now with pocketbase). would be nicer than view collection i think.
maybe the computed field can be defined in sql? when registering in the plugin?