How SHOULD we delete PackageQuery and Install links with contains? #14
-
@konstantin Dyachenko#8793 , if we delete PackageQuery and Install this way: await deep.delete({
up: {
tree_id: {
_id: ['@deep-foundation/core', 'containTree']
},
parent: {
type_id: {
_id: ['@deep-foundation/core', 'Contain']
},
to: {
_or: [
{
type_id: {
_id: ['@deep-foundation/npm-packager', 'Install']
}
},
{
type_id: {
_id: ['@deep-foundation/core', 'PackageQuery']
}
}
]
}
}
}
}) Then the packages that were installed by using Install link will be deleted too. How can we avoid this? How SHOULD we delete only PacakgeQuery and Install links and contains to then? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
No, delete down by contain tree does not delete I suggest creating a query, that shows all links after its creation. Then you should install the smallest possible package and carefully watch what links are created. Contain tree may delete only links in that tree, but there are more links between Install and Package which will be kept as invisible garbage. |
Beta Was this translation helpful? Give feedback.
No, delete down by contain tree does not delete
Package
links, at least when these are created by Packager UI. I have no problem deletingPackageQuery
and Install links by using delete down on two contains - to Install and toPackageQuery
links.I suggest creating a query, that shows all links after its creation. Then you should install the smallest possible package and carefully watch what links are created. Contain tree may delete only links in that tree, but there are more links between Install and Package which will be kept as invisible garbage.