AsData type delegates its schema instance implementation to its non-AsData counterpart.

[Unisay]

Better way of defining HasSchema instance as explained here.

[michaelpj]

And the test itself should change to no longer import the type from Blueprints.Lib, rigth?

[Unisay]

And the test itself should change to no longer import the type from Blueprints.Lib, rigth?

bummer:

the reason is that type-level (TF-driven unrolling of nested types) flattening is not driven by the HasSchema instance (its not enough), but it requires a Generic instance to work, but the AsData types don't have it...

[michaelpj]

Ugh. Then this is rather pointless. I don't see why it can't be driven by the HasSchema instances - indeed it seems like the instance head in this case tells us the nested types, but whatever.

[Unisay]

Ugh. Then this is rather pointless. I don't see why it can't be driven by the HasSchema instances - indeed it seems like the instance head in this case tells us the nested types, but whatever.

If only I knew about this difficulty with AsData in the beginning I wouldn't use the TF/Generic-based derivation machinery, I'd employ heavier gun (Template Haskell) 🤷🏼‍♂️