A quick summary of the current situation.
- With read component "id" the "metadata" is the declared responsible component.
- The FileFormatter reads the metadata and attempts to call getComponent on it using the storage class delegate.
- The generic PropertyList StorageClass doesn't have a delegate and so this raises TypeError.
- There is no useful delegate we could register for PropertyList that would understand what "id" component meant because we have no way to tell such a delegate which header should be used for that component.
What I think this means is that we need some alternate path to handling these cases such that if there is no delegate we use the composite delegate and ask it to get the value from the responsible component. This will likely need new API for StorageDelegate.
A quick summary of the current situation.
What I think this means is that we need some alternate path to handling these cases such that if there is no delegate we use the composite delegate and ask it to get the value from the responsible component. This will likely need new API for StorageDelegate.