-
Notifications
You must be signed in to change notification settings - Fork 477
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
feat(addon-commerce): InputCard
uses Maskito
instead of legacy text-mask
#4385
Conversation
Pull request was closed ✔️All saved screenshots (for current PR) were deleted 🗑️ |
projects/addon-commerce/components/input-card/input-card.component.ts
Outdated
Show resolved
Hide resolved
Visit the preview URL for this PR (updated for commit bcd235c): https://taiga-ui--pr4385-maskito-input-card-mz88kde6.web.app (expires Sat, 06 May 2023 08:54:53 GMT) 🔥 via Firebase Hosting GitHub Action 🌎 Sign: 4b5ece1e114386f6a105425ef799091475b249eb |
BundleMonFiles updated (1)
Unchanged files (5)
Total files change +62B +0.01% Groups updated (1)
Final result: ✅ View report in BundleMon website ➡️ |
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## main #4385 +/- ##
==========================================
- Coverage 61.07% 61.06% -0.01%
==========================================
Files 1650 1650
Lines 19313 19309 -4
Branches 2746 2745 -1
==========================================
- Hits 11796 11792 -4
Misses 7029 7029
Partials 488 488
Flags with carried forward coverage won't be shown. Click here to find out more.
☔ View full report in Codecov by Sentry. |
projects/addon-commerce/components/input-card/test/input-card.component.spec.ts
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What about input card inside InputCardGroup
?
projects/addon-commerce/components/input-card/input-card.component.ts
Outdated
Show resolved
Hide resolved
@waterplea I will do it in next separate PR |
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Partially solves #120
Does this PR introduce a breaking change?