Chris Roche

cc @btc

Sorry let me clarify more! If a message is unused in any capacity (not part of a RPC, not a field type), deleting the entire message is not a breaking...

Ultimately we do want to allow users to force changes to the lockfile, but our current setup doesn't even give them access to the file. The details aren't all that...

I'll work on the PR to have the error message be more correct. And at the end of the day it's not a huge deal, just philosophically different opinion on...

Sorry for the delayed response (Holidays 😅)! Will get to a patch in the coming weeks, but feel free to mention that Lyft is using it.

For details on enum aliasing: https://developers.google.com/protocol-buffers/docs/proto3#enum

Can we make this as an additive test (without modifying any of the existing ones)? The tests listed here were meant to catch regressions in the handling of the go_package...

Thanks for writing in! Yes, we are looking to add a `testutil` subpackage to make this easier/clearer with prebuilt mocks and what-have-you, as well as more docs in this vein....

Howdy! I'm not sure if we have any tests for multiline strings, but if it's not encoding them properly (or if it's slapping \n everywhere), it's probably best to support...

Can you point me to this optionality? I can't seem to find it in the HCL docs. Is this a HCLv2 only feature?