How to tackle multiple nested renames with both matchingSome and everyItem

[elpitero]

Hello
I recently started using chimney and during experiments I found a case where nested renames do not seem to work:

  case class A_inner_inner(fieldA_A: String)
  case class A_inner(fieldA: Option[A_inner_inner])
  case class A(field: List[A_inner])

  case class B_inner_inner(fieldB_B: String)
  case class B_inner(fieldB: Option[B_inner_inner])
  case class B(field: List[B_inner])

  private val transformer = Transformer.define[A, B]
    .withFieldRenamed(_.field.everyItem.fieldA, _.field.everyItem.fieldB)
    .withFieldRenamed(_.field.everyItem.fieldA.matchingSome.fieldA_A, _.field.everyItem.fieldB.matchingSome.fieldB_B)
    .enableMacrosLogging
    .buildTransformer

Compilation of code above fails with error:

 + Attempting expansion of rule ProductToProduct
                          + Resolved A_inner_inner getters: (`fieldA_A`: java.lang.String (ConstructorVal, declared)) and B_inner_inner constructor (`fieldB_B`: java.lang.String (ConstructorParameter, default = None)), using name-based matching
                          + B_inner_inner
                          |   field fieldB_B: renaming from _.matching[scala.Some[A_inner_inner]].value.fieldA_A is not allowed, try selecting only field names from _.field.everyItem.field.everyItem.fieldA.matching[scala.Some[A_inner_inner]].value (_.field.everyItem.field.everyItem.fieldA.matching[scala.Some[A_inner_inner]].value.field1.field2, etc)
                          | 

Notice double field in logs ( names from _.field.everyItem.field.everyItem.fieldA

To make this code compile it is enough to either remove Option from classes definition (and keep double nested withFieldRenamed but without matchingSome) or make fieldA and fieldB have the same name (have single withFieldRenamed).
I have read documentation, but I coundn't found any info about such limitation, but I could have missed something.
Is there any solution for this case?
I am using Scala 2.13.16 and Chimney 1.7.3

[MateuszKubuszok]

It's a bug, I believe that here and additional check would have to be made, to check if non-.field-ending path (Option/Either/Collection/Map) is a valid use case (in past it wasn't and they had to be enabled on an allow-list-like fashion).

[elpitero]

Thank you for your answer. I have found another case, where .withFieldRenamed does not work, but I'm whether this has the same cause or not.

case class A(f: List[A_Inner])
case class A_Inner(a: String)

case class B(f: Option[List[B_Inner]])
case class B_Inner(b: String]

val transformer = Transformer.define[A, B]
    .withFieldRenamed(_.f.everyItem.a, _.f.matchingSome.everyItem.b)
    .buildTransformer

It fails with error:

field value: renaming from _.everyItem.a is not allowed, try selecting only field names from _.f.matching[scala.Some[scala.collection.immutable.List[A_Inner]]].value.everyItem (_.f.matching[scala.Some[scala.collection.immutable.List[A_Inner]]].value.everyItem.field1.field2, etc)

As transformer can resolve that type A_Inner should be mapped to B_Inner, maybe it would be possible to implement .withFieldRenamed method for specific types: .withFieldRenamed[A_Inner, B_Inner](_.a, _.b).

[MateuszKubuszok]

I suspect it's the same thing, and it would require a fix in the same place.

[MateuszKubuszok]

If you are interested in fixing this issue, I can guide you. In the foreseeable future, I do not have time for Chimney maintenance, so I can reply and guide others but I am not doing any work here.