Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: Align cardholder name validation with Web #1108

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

borisprimer
Copy link
Contributor

@borisprimer borisprimer requested review from a team as code owners February 5, 2025 15:18
@borisprimer borisprimer changed the title Align cardholder name validation with Web chore: Align cardholder name validation with Web Feb 5, 2025
Copy link
Contributor

github-actions bot commented Feb 5, 2025

Warnings
⚠️ This PR doesn't seem to contain any updated Unit Test 🤔. Please consider double checking it.🙏
⚠️ Please assign someone aside from CODEOWNERS (@checkout-pci-reviewers) to review this PR.
⚠️

Sources/PrimerSDK/Classes/Core/Constants/Strings.swift#L1257 - Types should be nested at most 1 level deep (nesting)

⚠️

Sources/PrimerSDK/Classes/Core/Constants/Strings.swift#L1257 - Types should be nested at most 1 level deep (nesting)

⚠️

Sources/PrimerSDK/Classes/Core/Constants/Strings.swift#L1257 - Types should be nested at most 1 level deep (nesting)

⚠️

Sources/PrimerSDK/Classes/Core/Constants/Strings.swift#L1257 - Types should be nested at most 1 level deep (nesting)

⚠️

Sources/PrimerSDK/Classes/Core/Constants/Strings.swift#L1257 - Types should be nested at most 1 level deep (nesting)

⚠️

Sources/PrimerSDK/Classes/Core/Constants/Strings.swift#L1257 - Types should be nested at most 1 level deep (nesting)

⚠️

Sources/PrimerSDK/Classes/Core/Constants/Strings.swift#L1257 - Types should be nested at most 1 level deep (nesting)

⚠️

Sources/PrimerSDK/Classes/Core/Constants/Strings.swift#L1257 - Types should be nested at most 1 level deep (nesting)

⚠️

Sources/PrimerSDK/Classes/Core/Constants/Strings.swift#L1257 - Types should be nested at most 1 level deep (nesting)

⚠️

Sources/PrimerSDK/Classes/Core/Constants/Strings.swift#L1257 - Types should be nested at most 1 level deep (nesting)

⚠️

Sources/PrimerSDK/Classes/Core/Constants/Strings.swift#L1257 - Types should be nested at most 1 level deep (nesting)

⚠️

Sources/PrimerSDK/Classes/Core/Constants/Strings.swift#L1257 - Types should be nested at most 1 level deep (nesting)

⚠️

Sources/PrimerSDK/Classes/Core/Constants/Strings.swift#L1257 - Types should be nested at most 1 level deep (nesting)

⚠️

Sources/PrimerSDK/Classes/Core/Constants/Strings.swift#L1257 - Types should be nested at most 1 level deep (nesting)

⚠️

Sources/PrimerSDK/Classes/Core/Constants/Strings.swift#L1257 - Types should be nested at most 1 level deep (nesting)

⚠️

Sources/PrimerSDK/Classes/Core/Constants/Strings.swift#L1257 - Types should be nested at most 1 level deep (nesting)

⚠️

Sources/PrimerSDK/Classes/Core/Constants/Strings.swift#L1257 - Types should be nested at most 1 level deep (nesting)

⚠️

Sources/PrimerSDK/Classes/Core/Constants/Strings.swift#L1257 - Types should be nested at most 1 level deep (nesting)

⚠️

Sources/PrimerSDK/Classes/Core/Constants/Strings.swift#L1257 - Types should be nested at most 1 level deep (nesting)

⚠️

Sources/PrimerSDK/Classes/Core/Constants/Strings.swift#L1257 - Types should be nested at most 1 level deep (nesting)

⚠️

Sources/PrimerSDK/Classes/Core/Constants/Strings.swift#L1257 - Types should be nested at most 1 level deep (nesting)

⚠️

Sources/PrimerSDK/Classes/Core/Constants/Strings.swift#L1257 - Types should be nested at most 1 level deep (nesting)

Generated by 🚫 Danger Swift against c50c720

Copy link

sonarqubecloud bot commented Feb 5, 2025

Copy link
Contributor

github-actions bot commented Feb 5, 2025

@borisprimer borisprimer requested a review from NQuinn27 February 5, 2025 15:39
@borisprimer borisprimer self-assigned this Feb 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants