radryan1979 / wizardconjurer Goto Github PK

Implement options on the steps for an on enter/exit call a function option.

Make the module package management friendly.

Implement a way for the user to provide a template URL via the wizardServiceApi that overrides the default directive template.

#1 Request: Use arrays to store step data. I've had the need to traverse the steps for quick filtering/searching and objects and custom methods, while great for a single object don't lend for intuitive use when dealing with a collection of those objects.

When you use the previous and next buttons to navigate, it does not update the navbar buttons to reflect the active step.

Need a way to allow a directive within the wizard directive to update the buttons/steps/etc - implement a method the child directive can call that will broadcast/emit to the wizard-directive.

If you have two elements on the same page, the directive updates the visibility of the steps in both wizards.

Would love to have a feature where you can reveal or hide a step without having to remove it/add it back in.
Ideally the process would be;

1. Add ALL potential steps once.
2. As user progresses, if there's a scenario where an action they take dictates skipping a step, or skipping all remaining steps, then the current step suddenly becomes the last step. The 'next' button would change to 'submit', and all relevant wizard properties are set accordingly. We now have these scenarios in place where a choice on one step can change everything that follows.

Implement angular.element and remove jQuery dependencies.

When navigating away from a page with a wizard on it, the on destroy method causes an error.

After selecting a step using the navbar buttons, you can no longer use the next or previous buttons to navigate.

Refactor the current implementation using TypeScript - another branch perhaps.

Implement means in service API to allow user to customize the text of the previous, next and finish buttons.