Use template literal types to at least allow validating that non-nested-path dependencies arguments are valid

[helixbass]

Per helixbass/eslint-plugin-ad-hok#60, I'm not seeing a successful way to leverage template literal types to check whether path-style dependencies arguments are valid or not

But so can at least take an approach like:

type StringWithDot = `${string}.${string}`

type AddEffectOnPropFalsy = <
  TProps,
  TPropPath extends StringWithDot | (keyof TProps & string)
>(
  propPath: TPropPath,
  effectCallback: (props: TProps) => () => void | (() => void | undefined)
) => CurriedUnchangedProps<TProps>

to validate non-dotted dependencies arguments (perhaps in combination with an ESLint rule checking dotted dependencies arguments per that issue)?

[helixbass]

Playing around with Path types here

[helixbass]

Using the "hose to dirty string" technique here

[helixbass]

Neither Path types nor the "hose" technique seems to be working when applied to unresolved TProps generics (eg in ad-hok helpers)