feat: useController()

[ntucker]

Motivation

Consolidate, simplify hooks

Consistent interface between managers and hooks

Global referential equality available everywhere (managers and updaters)

Simplify and consolidate TTL and error concepts

Less code in hooks = less work on rendering leaf nodes

Icing on cake: ez migration to EndpointInterface and flexible args support for hooks

Future breaking changes can allow ez migration with version strings sent to useController('v2')

Solution

We're introducing fetch, invalidate, resetEntireStore today into experimental.

Full future plan:

const controller = useController();

// actions
controller.fetch(UserResource.detail(), { id }) // sideEffects means no throttle, otherwise throttle
controller.receive(payload, UserResource.detail(), { id })
controller.invalidate(UserResource.detail(), { id })
controller.resetEntireStore()
controller.subscribe(UserResource.detail(), { id })
controller.unsubscribe(UserResource.detail(), { id })
// posisble new
controller.abort(UserResource.detail(), { id }) // only aborts if in flight
// note: to force fetch of sideEffect: undefined - call abort first
// this should enable good offline/online managers

// retrieval
const state = useContext(StateContext);
const [value, expiresAt] = controller.getResponse(state, UserResource.detail(), { id })
const error = controller.getError(state, UserResource.detail(), { id })

[ljharb]

Suggested change

	return action.meta.promise as any;
	return action.meta.promise as Promise<unknown>;