hey! so i have two enum classes that don't directly depend on each other right now (obviously), but ...

# announcements

[xii]

hey! so i have two enum classes that don't directly depend on each other right now (obviously), but my idea is to make a relationship between the two, because they are actually directly related. let's say one is spell categories, and the other one is spells. so for example, a spell category could be fire, and the spells would only be fire-based spells (following on thread)

[xii]

how would one model this?
currently it's like

enum class SpellType {
FIRE, WATER
}
enum class Spell {
FIREBALL, WATERBALL
}

[xii]

but of course this doesn't fulfill my initial condition because you could do something like this

class SpellCaster{
  val spellType: SpellType
  val spells: List<Spell>
}

and have a water spell caster have fire spells

[xii]

i hope its clear enough

[nfrankel]

enum class SpellType {
    FIRE, WATER
}
sealed class Spell<SpellType> {
    class FIREBALL<FIRE>
    class WATERBALL<WATER>
}

[nfrankel]

i had to change the code a bit
because enum cannot have type parameter

[xii]

that's awesome

[xii]

so in the case of spellcaster, it would be something like this?:

[xii]

class SpellCaster(
    val spellType: SpellType,
    val spells: List<Spell<SpellType>>
)

? or how would you constrain it?

[xii]

in the spellcaster class itself

[nfrankel]

that depends
if you magus is only allowed to cast one type of spell
you could model it like this:

class SpellCaster<T : SpellType>{
    lateinit var spellType: T
    lateinit var spells: List<Spell<T>>
}

[xii]

i see, that's awesome, thank you

[xii]

my only concern is that i'm using javax persistence

@Enumerated(EnumType.STRING)

for some stuff, and i'm pretty sure it's gonna begin storing them as

FIREBALL<FIRE>

instead of as

FIREBALL

[xii]

because of the change from enum class to sealed

[nfrankel]

that’s another requirement 🙂

[nfrankel]

that you didn’t mention before

[nfrankel]

then, i’d avoid using enum

[xii]

yeah its just something i just noticed, sorry 😆

[nfrankel]

or if you want:

enum class SpellType {
    FIRE, WATER
}
abstract class Spell(val type: SpellType)

[xii]

this is perfect, thank you again