Songbooks #3
Loading…
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?
We wanted to provide users with the ability to group songs into specific songbooks. This would require:
...
This feels a lot like #2. Maybe we can reuse the functionality from tagging to create the songbooks from tags?
This could be achieved by adding the ability to create PDFs/
/bookviews from tags.changed title from Songbook to Songbook{+s+}
mentioned in merge request !7
I do like the idea of having one abstraction regarding tags and books. The first implementation however now ignores this and just implements books without tagging in mind.
The main difference seems to be the ownership, as tags are not limited to one profile. One could call books "user tags". 🤷
marked the checklist item Extension of the model with song books (a name) as completed
marked the checklist item A many-to-many relation to see whether a song is in a certain song book as completed
Added in !7.