You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When creating, updating, or deleting embedded documents within a parent Document that exists inside a Compendium pack, automatically infer the pack from the parent document.
#5937
Closed
aaclayton opened this issue
Sep 27, 2021
· 0 comments
When creating a document within a parent that itself is part of a compendium pack, that pack also needs to be specified explicitly. For example, in order to create an Item within an Actor in a compendium pack, you need to do
Having to specify the pack explicitly is redundant as it is only possible to create the embedded document inside the parent in that compendium pack anyways.
Additionally, this is already handled automatically when creating the embedded document via createEmbeddedDocuments.
In order to make this easier to use and also to harmonize the 2 ways of creating embedded documents, I suggest to infer the pack automatically from the parent if possible, in the same way that happens for createEmbeddedDocuments.
Priority/Importance
Pretty low priority as there are obvious workarounds. This is just to make the API a bit nicer / more consistent. But it should be pretty low effort, so it might be a good idea to just do it anyways.
The text was updated successfully, but these errors were encountered:
Originally in GitLab by @ghost91-
Feature Summary
When creating a document within a parent that itself is part of a compendium pack, that pack also needs to be specified explicitly. For example, in order to create an
Item
within anActor
in a compendium pack, you need to doHaving to specify the pack explicitly is redundant as it is only possible to create the embedded document inside the parent in that compendium pack anyways.
Additionally, this is already handled automatically when creating the embedded document via
createEmbeddedDocuments
.In order to make this easier to use and also to harmonize the 2 ways of creating embedded documents, I suggest to infer the pack automatically from the parent if possible, in the same way that happens for
createEmbeddedDocuments
.Priority/Importance
Pretty low priority as there are obvious workarounds. This is just to make the API a bit nicer / more consistent. But it should be pretty low effort, so it might be a good idea to just do it anyways.
The text was updated successfully, but these errors were encountered: