would we want to then express

name

as a special case of that?

name

is entirely special cased with the Target API and not treated as a normal

Field

. We pop it from

struct.kwargs()

before converting

HydratedStruct -> Target

. Rule authors can access the information via

tgt.address.target_name

, so it’s not necesssary to have the

Field

and it would be super tricky to get the

Field

working within the Target API framework, e.g. the default value being dynamic based on the physical location of the target

thanks!