AuditeMarlow

@lonerwolf, is this issue still relevant? If so, could you provide a full example illustrating the problem?

@asim, is this issue still relevant?

Unfortunately the Micro CLI does not support plugins and most likely will not support plugins in the near future due to the nature of how plugins are set up in...

What exactly is it that you had in mind? Get rid of the generator completely and instead build templates for the Micro CLI with conditionals based on the proto?

I'm having trouble picturing this still. I suppose the Micro CLI generated file should not reside in `proto`, but elsewhere considering it will in fact not be a protobuf generated...

> go get: go-micro.dev/v4/plugins/auth/[email protected]: parsing go.mod: module declares its path as: github.com/micro/go-micro but was required as: go-micro.dev/v4/plugins/auth/jwt The Module name for the JWT plugin is [`github.com/asim/go-micro/plugins/auth/jwt/v4`](https://github.com/asim/go-micro/blob/master/plugins/auth/jwt/go.mod).

As of right now, I'm not familiar with a method of removing blocks like you mentioned. In theory you could replace the default service registry with a custom noop implementation....

So far no example has been provided for the auth functionality. We are happy to accept PRs however.

I would personally prefer the hyphenated version as there's a clear separation of the words "Go" and "Micro". Would renaming the module not be a backwards incompatible change though? In...

Just for clarity's sake, the plan is to rename the module from `github.com/asim/go-micro/v3` to `go-micro.dev`? This means omitting the `v3` path from the module name, correct?