It would be useful to know what custom primitives were used to generate XLRs to know a minimal set of the types that would be needed to fully fill in the tree. The manifest would be the appropriate place to put this information. Functionally This should be done in the CLI when writing the manifests out. My suggestion would be to make a top level metaData object with a primitives key that maps to an array of strings.
It would be useful to know what custom primitives were used to generate XLRs to know a minimal set of the types that would be needed to fully fill in the tree. The manifest would be the appropriate place to put this information. Functionally This should be done in the CLI when writing the manifests out. My suggestion would be to make a top level
metaDataobject with aprimitiveskey that maps to an array of strings.