- Examples:
- User register wizard-based
- Replacement of express-router by emvici-router on an express app
- Share generated route as context for stacks
- #30 Wizard.Store.processedSteps is now saving
step.id
instead ofstep.name
- Implementation of prerequisites feature for route filtering
- Added methods on #WizardRoute.prototype for allowing step's data store
- Updated dependencies
- Lot of bugfixes
- Router's route dispatching approach refactored
- Added a short-circuit feature for router.
- Added
strictNavigation
option to replacelockdown
feature on WizardRoutes. - Multiple fixes on wizard routes
- Not defined variable fix
- Minor wizard fixes
- Minor wizard fixes
next()
should always exit router on stack end, unless we specify 'route'. Example:next( 'route' )
- Fixed bug into
router.addRoutes
because of a mispelling variable reference - Set
emvici_router
name to middleware function for debug proposes Router.dispatch[next]
should only try to find another route if a string 'route' is specified!
- Add stacks per param, similar to
.param
API provided by express - Changed name of each Class to
function.name
for better debugs
- Stack-based route full support
- Wizard-based route basic support