Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Suggestion: Provide option for 'unpack' command that unpacks adventure documents into their subordinate component documents #46

Open
silvative opened this issue Mar 30, 2024 · 2 comments · May be fixed by #61
Open

Suggestion: Provide option for 'unpack' command that unpacks adventure documents into their subordinate component documents #46

silvative opened this issue Mar 30, 2024 · 2 comments · May be fixed by #61

Comments

@silvative
Copy link

While they're a single document in themselves, adventures are a bit of a special case and each one sort of functions as its own special compendium- it would be nice to have an option to get an individual file for each of the contained documents, rather than a single file for the entire adventure.
@silvative silvative changed the title Suggestion: Provide command option for 'unpack' that unpacks adventure documents into their subordinate component documents Suggestion: Provide option for 'unpack' command that unpacks adventure documents into their subordinate component documents Mar 30, 2024
@p4535992
Copy link

p4535992 commented Apr 9, 2024

+1

arbron added a commit to arbron/foundryvtt-cli that referenced this issue Feb 20, 2025
@arbron
[foundryvtt#46] Extract documents within adventures into separate files
d957a15 
Adds a new `expandAdventures` option that extracts all of the
documents within an adventure into their own files when extracting
from LevelDB. When this option is selected each individual
document in the adventure is extracted as if they were primary
documents and gets `transformEntry` and `transformName` called on
them with an additional context object that contains information
on the adventure itself. The adventure is then saved with the
filenames for the written files in place of the whole objects.

When compiling back to NeDB or LevelDB, the CLI will check for any
strings within the adventure document and reassemble it from the
files listed.

Closes foundryvtt#46
arbron added a commit to arbron/foundryvtt-cli that referenced this issue Feb 20, 2025
@arbron
[foundryvtt#46] Extract documents within adventures into separate files
42d77e3 
Adds a new `expandAdventures` option that extracts all of the
documents within an adventure into their own files when extracting
from LevelDB. When this option is selected each individual
document in the adventure is extracted as if they were primary
documents and gets `transformEntry` and `transformName` called on
them with an additional context object that contains information
on the adventure itself. The adventure is then saved with the
filenames for the written files in place of the whole objects.

When compiling back to NeDB or LevelDB, the CLI will check for any
strings within the adventure document and reassemble it from the
files listed.

Closes foundryvtt#46
@arbron arbron linked a pull request Feb 20, 2025 that will close this issue
Open
@arbron
Copy link

arbron commented Feb 20, 2025

PR up for this: #61

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[#46] Extract documents within adventures into separate files arbron/foundryvtt-cli
3 participants
@p4535992 @arbron @silvative