In general, IDL chained structs act more like PODS, and their constitutent member variables are set one-by-one, rather than via a single parse() call or their constructors, which is normally how we pass a SerializationContext object from the enclosing type to the nested type.  Chained structs, which also enclose a SerializationContext object, bypass this mechanism, which can lead to inconsistent SerializationContext objects between the enclosing and nested types, and can cause silent failures especially if the nested chained struct is serializing/deserializing database name or namespace string types.

If the chained structs do not contain database name or namespace string types, and their SerializationContext objects are not consumed in any way, this may not actually pose a problem.  This is particularly true if the chained structs are used like PODS, so this ticket aims to first investigate if there are any chained structs that consume or forward for consumption their SerializationContext objects.