.proto3 input -> .ts3 output
See original GitHub issueThis worked great out of the box! So much nicer than protoc’s commonjs output! ❤️
I ran into one odd roadbump – it kept generating a .ts3
file, which Snowpack didn’t know to interpret as TypeScript. I finally figured out it’s because I’d named my file something.proto3
and that 3 was carried over. I’m fine just renaming my input file to .proto
for now to work around this.
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
Language Guide (proto3) | Protocol Buffers - Google Developers
It covers the proto3 version of the protocol buffers language: for information on ... to an output stream, and parsing your messages from...
Read more >protobuf-ts/MANUAL.md at master - GitHub
An "unary" call takes exactly one input messsage and returns exactly one output message. It is one of the four RPC method types...
Read more >protoc-gen-ts - bytemeta
protoc-gen-ts repo issues. ... proto3 fields unnecessarily serialized. NfNitLoop. NfNitLoop CLOSED · Updated 2 years ago .proto3 input -> .ts3 output.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I am glad that you have solved your problem with this plugin. I would appreciate a star though 😄
Also, that is a good catch and I think it is related to this line https://github.com/thesayyn/protoc-gen-ts/blob/db9e02e6e2f56d2fa55d21f02b681ed93228ccbd/src/index.js#L1646
I’ll fix it this weekend.
Oh I see. This should be fixed in 0.3.0.