Support for actionId and handle components in REDIRECT steps #976
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.
Issue
wso2/product-is#25415
This pull request introduces support for an explicit
actionIdproperty in theComponentmodel, ensuring that button components have a clear action identifier. It also improves the conversion logic to consistently setactionIdfor buttons, updates API documentation examples, and refines handling of component lists in data conversion.Model and API improvements:
actionIdproperty to theComponentclass and ensured it is included in equality, hash, and string methods. [1] [2] [3] [4] [5]flow-execution.yaml) and Java annotations to use consistent examples foridandactionId, clarifying documentation. [1] [2] [3] [4]Conversion logic enhancements:
Utils.java, modified theconvertToComponentmethod to setactionIdto the component'sidfor button components, ensuring correct action mapping.componentslist inconvertToDatato avoid nulls and ensure empty lists are returned when appropriate.Code maintenance:
ArrayListinUtils.javato support new logic.