fluxible-resolver is built on top of react-resolver and connectToStores, allowing you to fetch prop values asynchronously before rendering your component, using fluxible actions and stores. In addition, you can declare dependencies on other resolvers so you can assume they are available when resolving your depenent prop.
You can think of fluxible-resolve like a CDN. When a request comes in first we check if we already have the content stored in our cache. If so, great, return the content. If not, fetch it from the original source. In this case, the incoming request is React rendering your component, the cache is
isResolved, and the http client that fetches from the original source is
Takes an object of resolvers, keyed by the name of the prop they are resolving, and doesn't render the underlying component until all data is available.
Array<String>: optional array of strings, naming either props (must be specified via propTypes) or other resolvers.
(FluxibleContext, Array<any>): any: required function that takes context and dependency values and returns the current value for the prop.
(any, Array<any>): boolean: optional function which takes the current value and the dependency values and returns whether the prop value is available.
(FluxibleContext, Array<any>): Promise: required fluxible action that takes the arry of dependency values as the payload and fetches the value.
Array<FluxibleStore | String>: required array of fluxible stores, or store names.
;const resolvers =propName:dependencies: // optionalcontext!!currentValue // optional - by default checks if currentValue is definedcontextstores: PropStore // getStateFromStores can only call context.getStore for stores listed here;/*** propTypes are optional, but are required if you want a resolver to depend* on a prop passed to the container rather than depending on another resolver**/const propTypes =;const Container = Component;