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

feat: use event payload type for emitSnapKeyringEvent #203

Merged
merged 7 commits into from
Mar 25, 2025

Conversation

ccharly
Copy link
Contributor

@ccharly ccharly commented Feb 11, 2025

Currently, the emitSnapKeyringEvent iss using a generic payload type (like a Record<string, Json>). We were already using superstruct under the hood to check that payload, but the error was then thrown at runtime.

This new implementation allows to extract the actual payload type associated with the event to get errors at compile-time.

@ccharly ccharly requested a review from a team as a code owner February 11, 2025 17:35
@ccharly ccharly changed the title feat: use event payload type for emitSnapKeyringEvent feat: use event payload type for emitSnapKeyringEvent Feb 12, 2025
@ccharly ccharly force-pushed the feat/typed-emit-keyring-event branch 3 times, most recently from d4f37e4 to aa77804 Compare February 12, 2025 16:38
@ccharly ccharly force-pushed the feat/typed-emit-keyring-event branch from a5faeea to 2466e03 Compare February 20, 2025 14:05
@ccharly ccharly force-pushed the feat/typed-emit-keyring-event branch from 2466e03 to 2a26eea Compare March 25, 2025 08:44
@ccharly ccharly force-pushed the feat/typed-emit-keyring-event branch from 2a26eea to db4d703 Compare March 25, 2025 09:05
@ccharly ccharly added this pull request to the merge queue Mar 25, 2025
Merged via the queue into main with commit 6f94f48 Mar 25, 2025
31 checks passed
@ccharly ccharly deleted the feat/typed-emit-keyring-event branch March 25, 2025 10:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants