You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to allow the unhappy path lambdas to have their natural return types As a pathing manager I want to pass in the assignment to the success branch rather than dereferencing.
Acceptance Criteria
Scenario: set map callback in pathing manager should set response in a lambda GIVEN set map callback in pathing manager is running WHEN the happy path succeeds THEN the response message should be set in a lambda given to and_then AND the unhappy path should have return paths that don't force a SetMap::Response when then don't need it.
Need
In order to allow the unhappy path lambdas to have their natural return types
As a pathing manager
I want to pass in the assignment to the success branch rather than dereferencing.
Acceptance Criteria
Scenario: set map callback in pathing manager should set response in a lambda
GIVEN set map callback in pathing manager is running
WHEN the happy path succeeds
THEN the response message should be set in a lambda given to
and_then
AND the unhappy path should have return paths that don't force a
SetMap::Response
when then don't need it.Tasks
Notes
pathing_manager
set map callback should not dereference theexpected
https://github.com/PickNikRobotics/ros_testing_templates/blob/ros2/functional_programming_tests/src/pathing_manager.cpp#L52-L57
This forces the
or_else
clauses to have a particular return type, which doesn't make sense in context.References:
The text was updated successfully, but these errors were encountered: