This is fine in this context.  It's taking computing the velocity from the PathDesired UAVO which either comes from PathPlanner or ManualControlCommand.  The paths library takes that black box and computes the 3D velocity requested.