New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEATURE] Nested series #280
Comments
I am very interested in this feature. However, it would be nice if it could take folder structures of arbitrary depth into account. My use case includes TTRPG books, where I would need a deeper structure:
Example: |
I'm not sure I understand the scenario you're asking about. For my own clarity, is the ask:
It might be helpful to see an example of what you might expect the library to look like with your example. Copy and paste if you'd likeROOT
|-- Symbaroum
| |-- v1
| | |-- Adventures
| | | |-- The Chronicles of the Copper Crown
| | | | |-- Part 1 - The Promised Land.pdf
| | | | |-- Part 2 - The Promised Land.pdf
| | | | |-- etc.
| | |-- Some Other Adventure
| | | |-- Some Other Adventure.pdf
| | | |-- etc. {
"library": {
"name": "Symbaroum",
"series": [
{
"name": "...",
"subseries": [
{
"name": "..",
},
{
"name": "..",
"subseries": [
// etc
]
}
]
},
]
}
} |
Yes, exactly! Sorry if I have not made myself clear. I would also prefer your third - and your previously intended - variant. Deeply nested series/subseries would allow for very flexible structuring, which would stand out from the alternative solutions. |
Awesome, that works perfectly then since it aligns with my original plan 😅 I'm not sure if/how you are running Stump, but the |
Is your feature request related to a problem? Please describe.
Support a new library pattern that allows for generating of nested series
Additional context
See #254 (comment) for more context
The text was updated successfully, but these errors were encountered: