Derived field with parameterized type causes failure

[arouel]

When adding a @Derived field of a parameterized type the generated repository cannot be compiled due to a weird type token.

import java.util.HashMap;
import java.util.Map;
import java.util.Set;

import org.immutables.gson.Gson.TypeAdapters;
import org.immutables.mongo.Mongo.Repository;
import org.immutables.value.Value.Derived;
import org.immutables.value.Value.Immutable;

@Immutable
@Repository
@TypeAdapters
abstract class Value {

    abstract String some();

    abstract String fields();

    @Derived
    Map<String, Set<Long>> derivedFieldToBeStoredInMongo() {
        return new HashMap<>();
    }

}

The Serialization definition of the generated repository.

  @Generated(from = "_Value", generator = "Repositories")
  private static class Serialization {
    final Encoder<Map<java.lang.String, java.lang.String>> derivedFieldToBeStoredInMongoEncoder;
    final CodecRegistry registry;
    final String someName;
    final String fieldsName;
    final String derivedFieldToBeStoredInMongoName;

    Serialization(CodecRegistry registry, RepositorySetup.FieldNamingStrategy fieldNamingStrategy) {
      this.registry = registry;
      this.derivedFieldToBeStoredInMongoEncoder = this.registry.get((TypeToken<Map<java.lang.String, java.lang.String>>) TypeToken.getParameterized(Map.class, java.lang.String.class, java.lang.String.class));
      this.someName = translateName(fieldNamingStrategy, "some");
      this.fieldsName = translateName(fieldNamingStrategy, "fields");
      this.derivedFieldToBeStoredInMongoName = translateName(fieldNamingStrategy, "derivedFieldToBeStoredInMongo");
    }

    @Generated(from = "_Value", generator = "Repositories")
    static final class ValueNamingFields {
      public java.lang.String some;
      public java.lang.String fields;
      public Map<java.lang.String, java.lang.String> derivedFieldToBeStoredInMongo;
    }

    private static String translateName(RepositorySetup.FieldNamingStrategy fieldNamingStrategy, String fieldName) {
      try {
        return fieldNamingStrategy.translateName(
            ValueNamingFields.class.getField(fieldName));
      } catch (NoSuchFieldException noSuchField) {
        throw new AssertionError(noSuchField);
      }
    }
  }

[asereda-gs]

@arouel is there anything that prevents you from using criteria ?

Most of the efforts are spent on improving criteria API rather than fixing bugs with mongo repositories.

[arouel]

@asereda-gs the only thing preventing us is the time to migrate everything to the new API. We have a quite large code base based on mongo repositories.