#480 Automatic Coproduct Rename from/to Protobuf GeneratedEnum

[saeltz]

I'm not entirely happy with the TransformedNamesComparison because it matches too broadly. I'm open for better suggestions.

I want to achieve a comparison for the following:

enum Field {
  FIELD_UNSPECIFIED = 0;
  FIELD_CASE_ONE = 1;
  FIELD_CASE_TWO = 2;
}

From/To

enum Field:
  case One, Two

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.20%. Comparing base (2df4291) to head (57d6c6f).

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #489      +/-   ##
==========================================
+ Coverage   90.06%   90.20%   +0.13%     
==========================================
  Files         125      125              
  Lines        4763     4759       -4     
  Branches      430      412      -18     
==========================================
+ Hits         4290     4293       +3     
+ Misses        473      466       -7     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[MateuszKubuszok]

Thank you for the effort! I left a comment.

[MateuszKubuszok]

I would either name it CamelCaseUnderscoreCaseEquality (to e.g. use this with Java enums as well, maybe it should be a default for it? Maybe it should be named JavaEnumAware?) or keep it in chimneyProtobuf module. I wouldn't put some integration-specific conventions in the core package.

[MateuszKubuszok]

Hey @saeltz 👋 , do you still want to work on this?

[saeltz]

Hey @MateuszKubuszok, this currently matches too broadly. For this special use case I would probably rather go for something like moia-oss/teleproto#326 by @lbialy.

[MateuszKubuszok]

@saeltz - if you want to use Chimney in your macro-logic, with 1.1.0 it would be possible to just use Chimney macros directly. Please, open a discussion if you are interested in this.