From @dubadub in Discord:
Probably at some point we would need to add a function to return file path where it found the key (I'm thinking about the case when the server returns user path for downloading file).
From me:
Yes, having more traceability into what it finds would be desirable, if for nothing else than being able to debug it. I wonder how that would look. Perhaps rather than return just the DeserializeOwned value, it could return a struct/handle that contains that as well as some extra tracing informaiton.
Then again without some dyn shenanigans I don't think I can store that in a struct together (fields can't just be traits afaik)
So I'm thinking create a second get() function that returns a struct we create. That would have both a pointer to the relevant deserialized element as well as the path it found it at.
From @dubadub in Discord:
From me:
So I'm thinking create a second
get()function that returns a struct we create. That would have both a pointer to the relevant deserialized element as well as the path it found it at.