A way to set level preserve_unknown_fields for the project level. about scalapb HOT 4 CLOSED

Hi @ianlintner , see this FAQ for why we chose not to have global options: https://scalapb.github.io/docs/faq#why-a-certain-customization-is-not-available-as-a-global-generator-parameter

Since you're aware this feature can be enabled for an entire package, what is the use case that isn't solved by this?

from scalapb.

I have an external protobuf library that is language agnostic that has a few dozen different namespaces without a shared root.

My scala project uses the external protobuf library now requires 20+ additional package configurations to match the pre 0.10.0 behavior.

Is there another solution to make a better developer experience when working with large proto libs?

from scalapb.

Would it work for you if there was a way to easily list all the top-level namespaces in package scoped options? Something like:

import "scalapb/scalapb.proto";

option (scalapb.options) = {
  scope: PACKAGE
  preserve_unknown_fields: false
  apply_to_packages: ["pkg1", "pkg2", "pkg3", ...]  # <-- new proposed feature
};

Out of curiosity, why not enable unknown fields for the Scala project? It may require changes if you used pattern matching, but other than that, I think it should be considered to enable it.

from scalapb.

Closing due to inactivity. Feel free to comment if the issue is still relevant.

from scalapb.