Nested ValueEnums don't work

I’m converting some of my stuff to the StringEnumEntry, (Thanks!) and I’m noticing a few things I did earlier (With stock EnumEntry) that don’t work with this. It’s quite possible the answers will be “don’t do that”.

I’d set up an object with all the objects associated with a use case. This allowed a single easy import statement to get all the relevant symbols. This doesn’t compile:

sealed abstract class ParameterName(val value: String) extends StringEnumEntry
object ParameterConstants extends StringEnum[ParameterName] {
  object FOO extends ParameterName("foo")

  override def values = findValues

  sealed abstract class FooValue(val value: String) extends StringEnumEntry
  object FooValues extends StringEnum[FooValue] {
    object A extends FooValue("a")
    object B extends FooValue("b")

    override def values = findValues
  }

}

[LPTK]

Agreed. I may look into a prototype to find out when I have time 😉

[lloydmeta]

Added support for this by switching a few things in the way constructor parameters are resolved. Added a test case for it too.

To use it, update to 1.4.11.