Description
Not everyone wants to lazy load entire state definitions or trees of states.
Consider a lazy load API that allows anything such as components to be lazy loaded, without lazy loading a state definition.
The primary concern is that the current API expects the lazy load function to replace the current state. Essentially, if they state has a lazy load property, it is considered a future state and will be removed when it is loaded lazily and replaced by the new definition.
An alternate possibility is to keep a lazy load as is but do not use that as the criteria for State replacement. Instead, perhaps the states name suffix of .** could indicate that the state is a future state, for example: mail.** indicates that this state will be replaced by a new definition after lazy load is complete.