Cannot initialize enum value with static final Java field

[REASY]

I would want to wrap constants from Java to provide more context not just pure numbers. Imagine I have the following in Java:

package schema;

public final class PointCloudType {
    public static final byte XXX = 0;
    public static final byte PCL_PointWithLabel = 1;
    public static final byte PCL_XYZ = 2;
    public static final String[] names = new String[]{"XXX", "PCL_PointWithLabel", "PCL_XYZ"};

    private PointCloudType() {
    }

    public static String name(int e) {
        return names[e];
    }
}

If I create ByteEnumEntry to wrap them:

package com.motional.platform.map.data.spark.tiler3d.models

import enumeratum.values.{ByteEnum, ByteEnumEntry}

sealed abstract class PointCloudType(val value: Byte) extends ByteEnumEntry

object PointCloudType extends ByteEnum[PointCloudType] {
  val values = findValues

  case object PCL_PointWithLabel extends PointCloudType(value = schema.PointCloudType.PCL_PointWithLabel)

  case object PCL_XYZ extends PointCloudType(value = schema.PointCloudType.PCL_XYZ)
}

I'll get a compilation error:

It looks like not all of the members have a literal/constant 'value:int' declaration, namely: object PCL_PointWithLabel, object PCL_XYZ.

This can happen if:

- The aforementioned members have their `value` supplied by a variable, or otherwise defined as a method

If none of the above apply to your case, it's likely you have discovered an issue with Enumeratum, so please file an issue :)
         
  val values = findValues

[lloydmeta]

So, the findValues for value enums require that their values be supplied as a literal, and not a variable or a reference, which is what value = schema.PointCloudType.PCL_PointWithLabel is doing.

[REASY]

@lloydmeta thanks for the response.

Do you think new behavior can be added? Or it will complicate enumeratum tying to resolve reference?

[lloydmeta]

Hmm, it might be possible? I haven't given it a stab, but you're welcome to give it a try!