Clarification on SendPaymentV2 and dest_features

[gtochim]

When hitting SendPaymentV2 and providing an invoice in the payment_request field, the destination feature vector is decoded in zpay32/decode.go . No validation is done. However, if one doesn't provide an invoice and provides among other necessary fields, a dest_features , this vector is parsed in the router_backend via UnmarshalFeatures, which does some validation, e.g. checking that both OPT and REQ bits are not set at the same time.

Is this difference in behavior intended? For what reason?

[ellemouton]

@gtochim - im assuming that this was just an oversight :)