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

FINERACT-2169: New command processing infrastructure #4281

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

@vidakovic vidakovic self-assigned this Jan 23, 2025
@vidakovic vidakovic force-pushed the feature/FINERACT-2169 branch from 9fa080d to 300f88a Compare January 23, 2025 10:07
@@ -0,0 +1,35 @@
⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⣰⣿⣷⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀
Copy link
Contributor

Choose a reason for hiding this comment

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

an easter egg? nice 😀

Copy link
Contributor Author

Choose a reason for hiding this comment

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

... ah... Kristof... can't hide anything from your eyes 😄

@vidakovic vidakovic force-pushed the feature/FINERACT-2169 branch from 300f88a to 558bcc9 Compare January 25, 2025 11:10

@Override
public <REQ, RES> Supplier<RES> execute(Command<REQ> command) {
CompletableFuture<RES> future = null;

Choose a reason for hiding this comment

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

I think this is unnecessary😅, probably be better init on single line.. I think it will be better at least for code style

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Sure... we save one line.

@meonkeys
Copy link
Contributor

meonkeys commented Feb 5, 2025

v1.11 is coming soon... we don't want this in 1.11, right? Just trying to keep an eye on this since I'm working with James on the v1.11 release today.

@vidakovic
Copy link
Contributor Author

@meonkeys ... I'd say let's leave this one out of 1.11 ... it would have no impact, but still, let's keep this one out. Feel free to progress with the release.

@meonkeys
Copy link
Contributor

meonkeys commented Feb 5, 2025

Perfect, thanks @vidakovic . Should be easy as long as it isn't merged into develop before we branch for v1.11 in about a couple weeks.

Cc: @jdailey

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