iliaidakiev / hg-resolvers Goto Github PK

Probably it's better to directly reffer the public-api.ts instead the dist of the project, so that when you develop the lib the changes can be applied in the demo project, without the need of rebuilding the project

AsyncRenderComponent is missing from the public API, I think it will be useful to be public, for easier interactions with the component.

Current behavior:

In order to re-load the async renderer, new data must be passed to the refresh$ Subject inside AsyncRenderComponent, which triggers all necessary loads.

Suggestion

Probably it will be more robust if instead

asyncRef.refresh$.next();

we have something more like

asyncRef.refresh();

which then will handle all necessary load-related operations internally.

If you toggle the shouldSkip state of already SETTLED resolver it's returned to RESOLVING state.