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.

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

DDST-382: Subscriber to handle deletion of related Embargoes when a n… #13

Closed
wants to merge 3 commits into from

Conversation

Prashant-bd
Copy link
Contributor

…ode is deleted

Copy link

@adam-vessey adam-vessey left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not entirely sure this is desirable, and definitely not in some other module? Like, if this behaviour is expected, it should probably be implemented in embargo proper.

* The Islandora object node being deleted.
*/
public function deleteAssociatedCustomEntity(NodeInterface $node): void {
$custom_entity_storage = $this->entityTypeManager->getStorage('embargo');

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This would effectively be creating a dependency on the embargo module, yeah? Probably not desired.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@adam-vessey please suggest in which module I can implement this. https://github.com/discoverygarden/embargo module?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would be more of the target, yes. Still not convinced that such functionality is desired.

Like, something like a scan to find occurrences of ::getEmbargoedNode() that don't account for it being able to be NULL might be more in order?

The ticket is more about error suppression than data maintenance that this PR is getting into, or so I read it. As in, much like discoverygarden/embargo#41 , might also need to hit: https://github.com/discoverygarden/embargo/blob/a075aa4a994472666adf9cdd1af48891fb675323/src/Plugin/search_api/processor/EmbargoJoinProcessor.php#L230

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants