Doria Keung

A new version of the extension that uses the LSP is now available as a pre-release version, if this issue persists on this new version, please feel free to re-open....

Floated the idea to @mfridman, some open questions from our chat: - The replace directive would/should be reflected in `buf.lock` - What should the behaviour with `buf push` be? -...

For the example provided in the description, `buf.build/grpc-ecosystem/grpc-gateway` for `buf.build/grpc-ecosystem/protoc-gen-swagger`, the module-level replacement is insufficient, since the proto packages have been renamed. This would need to handle package-level replacement.

So `buf` requires `buf.build/gen/go/bufbuild/protovalidate/protocolbuffers/go` for our lint rules to check protovalidate options, and we try to keep the packages on the CLI as up-to-date as possible. Do you mind elaborating...

This is currently not specced out. In the meantime, we have https://github.com/bufbuild/buf-plugin-protovalidate-strict

> Should we close this now? I think we should close this, I don't think we're intending on restricting the client.

We are currently working on an overhaul of our compiler, and along with that, we'll introduce support for edition 2024. I will keep this issue open and update when things...

Thank you for filing this issue! Currently, [managed mode](https://buf.build/docs/generate/managed-mode/) prioritises support for the built-in protoc plugins, however, I think this is a very reasonable request. We’re currently not able to...