Skip to content

payment screens: replace remaining any in expansion items and form payloads #1382

Description

@marassteiner

Context

Follow-up from review of #1275.

Pre-existing any in the two production files this PR touches. The PR does not introduce them; they still need to be reported because those files are in the diff.

Evidence

src/screens/payment-link.screen.tsx:393, :511, :531].filter((item) => item.text) as any

src/screens/payment-routes.screen.tsx:170updatePaymentLinksConfig(data: any)
:464, :602, :689 — same as any filter
:896onSubmit?: (data: any) => Promise<void>
:993(mergedData as any)[key] = value
:1023const request: any = {}

Suggested fix

Filter expansion items with the real component prop type and a type predicate. Type form submission and request construction with the SDK DTOs or Partial<…>; merge config through typed keys.

Related

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions