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

update docs on how to access public change tracking interfaces #1612

Merged
merged 3 commits into from
Feb 7, 2025

Conversation

JenniferStamm
Copy link
Contributor

No description provided.

@JenniferStamm JenniferStamm marked this pull request as ready for review February 3, 2025 13:34
@smahati smahati added this pull request to the merge queue Feb 7, 2025
Merged via the queue into main with commit 24fc57b Feb 7, 2025
4 checks passed
@smahati smahati deleted the publish-change-tracking-api branch February 7, 2025 15:04
result.listOf(Changes.class).forEach(c -> {
@After(event = ChangeTrackingService.CREATE_CHANGES)
void afterCreate(CreateChangesEventContext context) {
context.getChanges().forEach(c -> {
Copy link
Contributor

Choose a reason for hiding this comment

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

Are we sure context.getChanges is the same as context.get("result") earlier? I see CreateChangesEventContext also has a getResult() method. @vmikhailenko Can you please take a look at this?

Copy link
Contributor

Choose a reason for hiding this comment

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

Isn't result the only correct way to handle something on after-phase?

getResult().listOf(Changes.class) is the right way to do it.

Copy link
Contributor Author

@JenniferStamm JenniferStamm Feb 7, 2025

Choose a reason for hiding this comment

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

I'll open another PR to fix it 🫡

edit, here it is: #1631

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.

4 participants