More TypeScript updates

[Jessidhia]

Addresses what I could from #383, and adds types for useChain.

[Jessidhia]

This change fixes autocomplete so it shows UseSpringBaseProps' properties on autocomplete

[Jessidhia]

This trick lets CSSProperties show up on autocomplete by default (as long as no property that you add is incompatible with CSSProperties itself; then it falls back to the other overloads)

[Jessidhia]

Added this to address #386

[Jessidhia]

Did immediate ever actually accept string[]? I can't find it in the code (in fact if it's an array it's just treated as always true in the Controller). This made it incompatible with SpringBaseProps so I had to remove the string[].

[drcmda]

@Kovensky No, immediate can be a boolean or a function returning boolean. This could be a left over.

[Jessidhia]

As I try to actually make use of this in a real project I noticed the type definition for useTransition is almost completely wrong 😓

I also wonder if it's possible to attach .interpolate to the output types. Might be again running into the "too generic for typescript" issue.

[drcmda]

transitions return Array<{ item, key, props, state }>, wheresare state can be enter|leave|update and props is an object that contains animated values (which can interpolate).

[Jessidhia]

Yeah, the output type is (almost) correct, but also very wrong because the input type is wrong.

First, it assumes that, like useSpring, the from is derived from the input props but that seems to not be the case with useTransition. Second, it puts the input object itself (minus some filtered props) as props instead of the union of the types of from / enter / update / leave.

[drcmda]

This we'll change soon, see: #393 i guess it should be useTransition(input, keys, config), just like useTrail(items, config). Can we anticipate this change already and exclude items, or will TS make it impossible to use?

[Jessidhia]

I think it has to be done at the same time, because items is currently required to be able to infer a generic argument.

(Somewhat related: initial is not working correctly, state.current.first is still false the first time transitions is calculated so initial is only used for not initial enters; the initial: null behavior is also unsupported)

[cdebotton]

@Kovensky I apologize if you've already considered this approach, but I had fairly primitive types I was using for just useSpring that were working with initial release of react-spring with hooks that supported chaining interpolate. Perhaps these might be helpful?

import { SpringConfig } from 'react-spring';

declare module 'react-spring' {
  type SpringOptions<T> = {
    config?: SpringConfig | ((key: string) => SpringConfig);
  } & T;

  type SpringSetter<T> = (options: Partial<SpringOptions<T>>) => void;

  type InterpolationOptions<T, U = T> = {
    range: T[];
    output: U[];
  };

  interface InterpolationFn<T> {
    <U>(options: InterpolationOptions<T, U>): Interpolation<U> & U & string;
    (interpolator: (params: T) => string): Interpolation<T> & T & string;
  }

  type Interpolation<T> = {
    interpolate: InterpolationFn<T>;
    getValue: () => T;
  } & T;

  type AnimatedValue<T> = { [K in keyof T]: Interpolation<T[K]> };

  export function useSpring<T>(
    options: SpringOptions<T>,
  ): [AnimatedValue<T>, SpringSetter<T>];
}

The new hooks may be more complex in a way that's prohibitive of using this.

[cdebotton]

I've actually opened up a PR that adds the typings for chains.

#400