2023-07-17
3046
#typescript
Ibiyemi Adewakun
174635
109
Jul 17, 2023 ⋅ 10 min read

Using Protobuf with TypeScript for data serialization

Ibiyemi Adewakun Ibiyemi is a full-stack developer from Lagos. When she's not writing code, she likes to read, listen to music, and put cute outfits together.

Recent posts:

Exploring Advanced Support For Vite 5 In Storybook 8

Exploring advanced support for Vite 5 in Storybook 8

Explore the latest updates in Storybook 8, focusing on its improved support for Vite 5 as a build tool.

Will Soares
Jun 20, 2024 ⋅ 5 min read
Exploring Angular 18's Redirectcommand Class And Let Block

Exploring Angular 18’s RedirectCommand class and @let block

Angular’s latest update brings greater control over redirects and the ability to define and assign variables within the template.

Lewis Cianci
Jun 19, 2024 ⋅ 6 min read
Showing Progress For Page Transitions In Next Js

Showing progress for page transitions in Next.js

Progress bars help create a smooth UX during page transitions in your Next.js app, informing users that their request is processing.

Elijah Agbonze
Jun 19, 2024 ⋅ 9 min read
Qwik Adoption Guide Overview Examples And Alternatives

Qwik adoption guide: Overview, examples, and alternatives

Qwik’s focus on performance, innovative features, and commitment to DX make it a fantastic choice for building high-performance web apps.

Fimber Elemuwa
Jun 18, 2024 ⋅ 10 min read
View all posts

2 Replies to "Using Protobuf with TypeScript for data serialization"

  1. Very nice article! One observation is that the deserialized output doesn’t exactly match the originally defined object. Specifically, the original enum string values are replaced with numeric values, e.g., { “platform”: “WHATSAPP” } became { “platform”: 0 }, and { “relationship”: “FRIEND” } became { “relationship”: 0 }. How do you reconcile this? Is there a way to preserve the original string values for enums?

Leave a Reply