LEAFNOTE ALTERNATIVE HOW TO

LEAFNOTE ALTERNATIVE HOW TO

Note: a bunch of hand-waviness here on how to isolate location-driven changes any already mounted components might see and prevent them from updating until acceptance. When all active middleware have accepted by either returned something other than false, or their promise has resolved, the new components will be rendered. If the navigate function is called asynchronously, the combined promise will be rejected, the navigation will be handled and the process will restart.If any middleware rejects, the combined promise will reject and location will be reverted.All other values returned will be considered acceptanceĪfter all middleware functions are called, any collected promises will be combined via Promise.all and read from a resource so they can trigger or be included in the concurrent transition when the author uses suspense.Errors thrown synchronously will not be caught (TBD).If the navigate function is called synchronously no further middleware functions will be called, the navigation will be handled and the process will restart.If the function returns a promise, the promise will be collected and the next middleware function called.If the function returns false (synchronously), the location will be reverted and no further middleware functions will be called.Note: Unlike data functions, a route’s middleware will be called for each navigation where that route is part of the match.

After the data functions have be called as normal, each middleware function will be called starting from the root, working toward the leaf. When a navigation occurs, the winning match (composed of one or more routes) will be determined. The function will allow returning false or a void promise. navigate: function to change the location.location: current location which is about to be rendered.data: value returned from the route’s data function.The function will take essentially the same parameters as the data function: not block data functions (the data could be used for middleware logic)Īdd a new property willEnter/ onMatch/ middleware/ ? (TBD) to route definitions (ie.prevent rendering a route based on response/thowing/rejecting.be asynchronous (ideally allow synchronous as well).I’ll lay out my thoughts and see if they make sense. I’ve been thinking about this and I believe we can do something here.

Leafnote alternative