Skip to content

RPP / Housekeeping / Context validation and nullable values #7430

Open
@RadoslavGeorgiev

Description

@RadoslavGeorgiev

Description

The payment process relies on everything required already being in the PaymentContext instance, but this might not always be the case. Let's keep this in mind, as we proceed, and use this issue to track parameters, which might be or not be present.

Ideally, populate_context_from_order should verify everything required.

For now this issue is blocked, as there are few input parameters are in use, and all of them are either guaranteed to be there, or handling is already in place.

Acceptance criteria

TBD

Testing instructions

TBD

Dev notes

TBD

Additional context

Epic: #6673
Project: paJDYF-9hL-p2

Metadata

Metadata

Assignees

No one assigned

    Labels

    category: coreWC Payments core related issues, where it’s obvious.category: engineeringFor product engineering, architecture work, tech debt and so on.category: projectsFor any issues which are part of any project, including bugs, enhancements, etc.component: checkoutIssues related to Checkoutfocus: checkout paymentsstatus: blockedThe issue is blocked from progressing, waiting for another piece of work to be done.status: on holdThe issue is currently not prioritized.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions