-
Notifications
You must be signed in to change notification settings - Fork 2
feat: Show access code errors and warnings in AccessCodeDetails
#243
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
Conversation
or `failed_to_remove_on_device`
… into add-access-code-errs-warns
… into add-access-code-errs-warns
… into add-access-code-errs-warns
src/lib/seam/components/AccessCodeDetails/AccessCodeDetails.tsx
Outdated
Show resolved
Hide resolved
src/lib/seam/components/AccessCodeDetails/AccessCodeDetails.tsx
Outdated
Show resolved
Hide resolved
razor-x
left a comment
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.
Will approve when SDK update is in
src/lib/seam/components/AccessCodeDetails/AccessCodeDetails.tsx
Outdated
Show resolved
Hide resolved
src/lib/seam/components/AccessCodeDetails/AccessCodeDetails.tsx
Outdated
Show resolved
Hide resolved
Co-authored-by: Evan Sosenko <evan@getseam.com>
… into add-access-code-errs-warns
… into add-access-code-errs-warns
| const errorFilter = ( | ||
| error: AccessCodeError | DeviceError | ConnectedAccountError | ||
| ): boolean => { | ||
| if ('is_access_code_error' in error && !error.is_access_code_error) |
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.
Nice. This makes me think we need to add type guards to the SDK for the different error types like we have for managed and unmanaged devices.
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.
Yep, that's a good idea!
Closes #239 • Should be good to merge after SDK updates, which are waiting on https://github.com/seamapi/seam-connect/issues/3455 (tests are expected to fail until then).