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
notification-ticket #3314
notification-ticket #3314
Conversation
0009604
to
0ebee88
Compare
return Optional.of((context, frame) -> { | ||
frame.pushCause(this.locatableBlock.get()); | ||
}); | ||
return Optional.of((context, frame) -> frame.pushCause(this.ticketSupplier.get())); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Like, something I could imagine being useful is:
return Optional.of((context, frame) -> {
if (parent instanceof ChangeBlock) {
frame.pushCause(((ChangeBlock) parent).original);
}
frame.pushCause(this.ticketSupplier.get());
});
to populate the original changeblock being changed (may look at potentially providing the parent transaction as a BlockTransaction accessor if available)
0ebee88
to
f2aa110
Compare
923fb24
to
46163ab
Compare
c66cfd3
to
f0b27a9
Compare
This revamps the previously meticulous brain-ache NotifyNeighborBlockEvent into a more streamlined event similar to ChangeBlock event. As the batching system has proven useful, this can safely expose directional suppliers without explicitly relying on legacy logic of "Always notify every neighbor on a target position" Signed-off-by: Gabriel Harris-Rouquette <gabizou@me.com>
f0b27a9
to
3596699
Compare
API | Sponge
Implements the new NotifyNeighborBlockEvent