-
Notifications
You must be signed in to change notification settings - Fork 481
Add get_parameter_or overload returning value or alternative #2973
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
Add get_parameter_or overload returning value or alternative #2973
Conversation
…r alternative Signed-off-by: Zheng Qu <quzhengrobot@gmail.com>
f7aa101 to
8ffcf53
Compare
fujitatomoya
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that is just fine to have this methods in LifecycleNode to keep the consistency with Node under current design.
can you also add the test to make sure this method works?
Signed-off-by: Zheng Qu <quzhengrobot@gmail.com>
|
Adding tests makes total sense. A new test has now been pushed in a separate commit. |
|
Pulls: #2973 |
|
@fujitatomoya do we need to backport this one ? |
|
@Mergifyio backport kilted jazzy humble |
✅ Backports have been created
|
Signed-off-by: Zheng Qu <quzhengrobot@gmail.com> (cherry picked from commit eb49444)
Signed-off-by: Zheng Qu <quzhengrobot@gmail.com> (cherry picked from commit eb49444)
Signed-off-by: Zheng Qu <quzhengrobot@gmail.com> (cherry picked from commit eb49444)
Description
LifecycleNodeis missing aget_parameter_orpublic function, which exists inNode.Is this user-facing behavior change?
Yes. It makes the behavior of
LifecycleNodemore consistent withNode.Did you use Generative AI?
No.