feat: Enhance Test data for Calculator CLI #985
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.
Pull Request
Summary
Enhance Test data for Calculator CLI. For below cases
Parameter Type Preservation in Macro Resolution
1.Simple Type Resolution
2.Complex Structure Resolution
Complex nested parameter structure case is not covered in code previously. Added fix for it.
Issue
Link to the issue(s) this PR addresses (e.g.,
Fixes #123orCloses #456). If no issue exists, explain why this change is necessary.Breaking Change?
If yes, describe the breaking change and its impact (e.g., API changes, behavior changes, or required updates for users).
Scope / Project
Specify the component, module, or project area affected by this change (e.g.,
docs,actions,workflows).Testcases for cli
Implementation Notes
Provide details on how the change was implemented, including any technical considerations, trade-offs, or notable design decisions. Leave blank if not applicable.
1.Added a pure-reference shortcut in processValue to detect values of the form ${param} and resolve them directly from Binding before template rendering.
This preserves the original object type (e.g., Map, List) and prevents unintended stringification by JinJava/Groovy.
Tests / Evidence
Describe how the changes were verified, including:
Tested with instance pipeline
Additional Notes
Include any extra information, such as:
Leave blank if not applicable.