Ban Object Values null | undefined | unknown

[codyduong]

I should add docs for banned object key values. This utility is used to parse through known results. As such there should be no point where the object provided returns a null | undefined | unknown | never in a key/value pair. These types all break the inference engine I made.

That or I change the inference engine to work on these. The only problem being is we often use these values as internal delimiters to decide when to stop deeply recursing through the object, soo...

Really, if the user of this library does not know the type, they should instead use any

[codyduong]

Due to the way I wrote the inference engine, any also blows it up.

This may be something I never fix, seeing as most users should know the return of their API data. If they don't, they should instead opt to type something as never.

[codyduong]

^ Nevermind, I was prematurely removing node navigations with this line. Even though we check later deeper down in the node if we are any. This should fix #2 and this issue.

nav/src/index.ts

Lines 43 to 44 in 21e7a94

	: O extends Record<string, infer OV> | Readonly<Record<string, infer OV>>
	? IsStrictlyAny<OV>