[Fix #1553] Initialize call field in generated Callxxx classes#1555
Merged
Conversation
fjtirado
force-pushed
the
Fix_#1553
branch
15 times, most recently
from
July 22, 2026 18:54
cd40c75 to
143326e
Compare
…ated Callxxx classes When using DSL, the call field is not set unless the DSL method implementation invokes either setCall or withCall, which current implementation is not actually doing, leading to the reported issue. Rather than changing a lot of fluent dsl classes both in sdk and experimental (recently moved to QFlow) it is better to fix in just one place, the generator of the problematic types. Signed-off-by: Francisco Javier Tirado Sarti <ftirados@ibm.com>
ricardozanini
approved these changes
Jul 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix #1553
When using DSL, the call field is not set unless the DSL method implementation invokes either setCall or withCall, which current implementation is not actually doing, leading to the reported issue.
Rather than changing a lot of fluent dsl classses both in sdk and experimental (recently moved to qflow) it is better to fix in just one place, the generator of the problematic types.