Is this project dead?

[Maximaximum]

Last commit dates 3 moths ago, and there are 80 open issues. Just wondering whether it's OK to use UI Router Extras and whether it is going to be maintained in future?

Also, it should support the latest version of ui router, I guess.

Thanks.

[christopherthielen]

Thanks for the interest in this project.

I don't want to abandon ui-router-extras. However, I confess that I haven't given it as much attention as it needs lately.

Here is why:

I am also the primary maintainer of the main ui-router project. UI-Router 1.0 is a pretty dramatic architecture shift, and I have been putting most of my free time making the 1.0 release happen as soon and smoothly as possible.

Much of the extras code relies on the implementation details of legacy ui-router 0.x version. This means compatibility with 1.0 will require some rewriting. The good news is that the rewrite should dramatically simplify the code.

Here is the path forward for UI-Router Extras:

• Transition: Deprecated; is replaced by core code in ui-router 1.0
• Future States: Deprecated, will be is replaced by core code in ui-router 1.0 (edited: 2016-10-20)
• Sticky States: Needs to be rewritten to support the new $view service
• Deep State Redirect: Needs to be rewritten as a Transition Hook
• Previous State: Needs to be rewritten as a Transition Hook
• StateVis: Already rewritten as a React app at http://github.com/ui-router/visualizer

Each project that needs to be rewritten should probably be created as its own github project, perhaps under the http://github.com/ui-router organization. My goal was to get 1.0 finalized (including Future States), and then attack the rewrites. Rewriting Sticky States will be the most challenging, but the rewrite should be vastly simpler to understand than the current codebase is.

For users who are unable to upgrade to ui-router 1.0, this project (in its current form) will still be valuable to them.

[Maximaximum]

Many thanks for the response!

Nice to know that some of the features will be included into the core.

Could you please give a hint on where to search for FutureStates in the new ui-router v.1.0?

[christopherthielen]

@Maximaximum I'm working on Future States for 1.0 core this week/next week

[Maximaximum]

Great! Thanks, I'll be really waiting for that feature!

[aloulouamine]

Is the current version compatible with ui-router 0.3.0 ?

Regards.

[christopherthielen]

Is the current version compatible with ui-router 0.3.0 ?

Yup.

[w-sz]

Hi @christopherthielen , thank you for your great ui-router extension. I started to use ui-router beta, when you expect to add sticky option there ?

[christopherthielen]

@witoldszpur you can track the progress here: https://github.com/angular-ui/ui-router/issues/2837

Currently I've only done some experimentation and don't have a solid timeline

[christopherthielen]

By the way all, Future States are in 1.0 core as of beta.2.

[lencyforce]

So how can I use Future States in ui-router beta 2? Is the API changed? Simply remove the dependency to ui-router-extras seems not work.

[lencyforce]

Looks like I found what I need in the unit test file...

[nmoinvaz]

I think it would be great if all the features were included in core.

[crgeee]

@christopherthielen any updates on sticky states compatibility with ui router 1.0? This feature is very important to me as I don't know of any alternatives to this type of support. Thanks for all your work

[christopherthielen]

@crgeee we're really close to a 1.0 final release. After that, I will devote time to implementing sticky states for 1.0

[crgeee]

@christopherthielen thanks for the quick update, looking forward to both

[wallzero]

Hey, I see 1.0.1 is the latest release. Has development on ui-router-extras begun? Thanks!

[christopherthielen]

• Future States: nearly complete
• Deep State Redirect: In development
• Sticky States: In development

[gauravmahto]

Can we get an update on the above items? The last commit that I see is about 2-3 months old. Looking forward to the Sticky States and the Deep State Redirect.

[christopherthielen]

@gauravmahto

• Future states are complete in 1.0.0-rc.1.
• Sticky states are complete and at their final home: https://github.com/ui-router/sticky-states
• DSR is complete but hasn't been moved to its final home yet.

[RavishankarMSGR]

Hi @christopherthielen , I am trying to migrate my application from angular1.3x to 1.5x, I have upgraded angular-ui-router: 0.2x to @uirouter/angularjs:1.0x. I followed the guidelines(https://ui-router.github.io/blog/uirouter-for-angularjs-umd-bundles/) to upgrade uirouter and installed ui-router-core and ui-router-angularjs aswell. since in my application i was using ui-router-extras: 0.0.14(stickyStateProvider) which is deprecated alternatively i am trying to use @uirouter/sticky-states.

I am getting ( require.js:166 Uncaught Error: Script error for: @uirouter/core ) error after injecting both ui-router-core and ui-router-angularjs (Please consider me rookie if i had made a mistake)

     "shim": {
        "uiRouterCore": {
            "deps": ["angular"]
        },
        "angularUiRouter": {
            "deps": [
                "angular",
                "uiRouterCore"
            ]
        },
    }

Am i following the right approach in migrating my application, please help and shed some light

[christopherthielen]

@RavishankarMSGR I don't use requirejs, so I cannot provide any help with regards to that.

However, I do suspect that in your config, uiRouterCore should be @uirouter/core and angularUiRouter should be @uirouter/angularjs (sticky states looks for '@uirouter/core')

[RavishankarMSGR]

@christopherthielen Many Thanks. Your suspect was right, Worked for me. corrected the path issue and injected the sticky states for ui-router 1.x