TreeNodes are generated for types that aren't actually components

I’m not sure if this is actually a bug so feel free to correct me. I noticed that treehouse is generating TreeNodes for enums even when they’re not supposed to be used like a component in the view hierarchy. Here’s an example from Cash App:

// Enum:
@Node(3)
@Serializable
@SerialName("DialogAction")
data class DialogAction(...) : Action() {
  @Node(14)
  enum class ButtonStyle {
    @Property(1)
    STANDARD,

    @Property(2)
    DESTRUCTIVE,
  }

// Generated code:
public interface ButtonStyle<T : Any> : TreeNode<T> {
  public override fun apply(diff: PropertyDiff): Unit {
    when (val tag = diff.tag) {
      else -> throw IllegalArgumentException("Unknown tag $tag")
    }
  }
}

The generated node also becomes part of the NodeFactory. Other examples in our project include BoxLayout, BoxLayoutDirection, and BoxLayoutItem which are all inner classes of Box. Is this expected?

[saket]

I like it!

[JakeWharton]

I’m moving the parser into its own module. Hold off for now.

@Node becomes @TypeId, but I was mulling @EntityId instead yesterday…