maybe type Data so it matches input? is that a breaking change?
definitely throw if data is a Map. that's definitely not what we want
validate that any key returned in data is an inputKey or storageKey of schemaFields and throw if an unexpected key is found
it wasn't working for userID in auth code example so checked for both inputKey and storageKey of fieldInfo but that means we could be sending extra and ignoring it now
Data
so it matches input? is that a breaking change?userID
in auth code example so checked for both inputKey and storageKey of fieldInfo but that means we could be sending extra and ignoring it nowfollow-up to https://github.com/lolopinto/ent/issues/1765