I guess that's what I'm saying. It was a mistake to make it an alias for both `'keyEncoding'` and `'valueEncoding'` and now it's mostly useless as an alias for `'valueEncoding'` and just adds overhead in the implementation. So maybe if we ignore it, it'll go away?!