sticky-states | Sticky states for UI-Router | Frontend Framework library

by christopherthielen TypeScript Version: Current License: MIT

X-Ray Key Features Code Snippets Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | sticky-states Summary

sticky-states is a TypeScript library typically used in User Interface, Frontend Framework applications. sticky-states has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

Deep State Redirect (DSR) is a marker you can add to a state definition. When a child state of the DSR marked state is activated, UI-Router Extras remembers the child and its parameters. The most-recently-activate child is remembered no matter where the user navigates in the state tree. When the DSR marked state is directly activated, UI-Router Extras will redirect to the remembered child state and parameters. One use case for DSR is a tabbed application. Each tab might contain an application module. Each tabs' state is marked as deepStateRedirect. When the user navigates into the tab, and drills down to a substate, DSR will remember the substate. The user can then navigate to other tabs (or somewhere else completely). When they click the original tab again, it will transition to the remembered ehild state and parameters of that tab, making it appear that the tab was never destructed. Deep State Redirect can be used with StickyStates, or on its own. If used with a Sticky State, the states will be reactivated, and the DOM will be unchanged (as opposed to the states being re-entered and controllers re-initialized).

Support

Quality

Security

License

Reuse

Support

sticky-states has a low active ecosystem.

It has 6 star(s) with 0 fork(s). There are 3 watchers for this library.

It had no major release in the last 6 months.

sticky-states has no issues reported. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of sticky-states is current.

Quality

sticky-states has no bugs reported.

Security

sticky-states has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

sticky-states is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

sticky-states releases are not available. You will need to build from source code and install.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of sticky-states

Get all kandi verified functions for this library.

sticky-states Key Features

No Key Features are available at this moment for sticky-states.

sticky-states Examples and Code Snippets

No Code Snippets are available at this moment for sticky-states.

Community Discussions

Trending Discussions on sticky-states

Angular Sticky States in Angular 2+

Ui-router State Change: Keep Controller and Scope but Destroy DOM

QUESTION

Angular Sticky States in Angular 2+

Asked 2018-Feb-05 at 07:28

I'm migrating a Angular 1.5.X app to Angular 4. In my App I use Angular Ui-Router Sticky State https://github.com/ui-router/sticky-states to avoid lose the content of my view when I made a navigation in some views of my APP but when I try to use this functionality in ng-router2 I can't find it. https://ui-router.github.io/ng2/tutorial/helloworld.

Some one know some router with similar function to Sticky State in Angular2+ or use the ui-router-ng2 to emulate the Sticky State.

...

ANSWER

Answered 2018-Feb-05 at 07:28

I found this answer on internet I cant remember the web but the solution is not mine.

Source https://stackoverflow.com/questions/45878698

QUESTION

Ui-router State Change: Keep Controller and Scope but Destroy DOM

Asked 2017-Mar-28 at 22:23

I am using ui-router 1.0.0-beta.3, angular 1.5. So far, ui-router is awesome!

I have a root state, with some child states so far, but I noticed switching between siblings (children of the same root parent) causes complete recreation of the state I transition/go to.

I'd like to keep the scope variables around because, in my app, users may toggle some buttons, enter dates, etc, then maybe switch to another state, do something, and switch back but now all their partial work is gone. I'd also like the option to be able to destroy DOM for "inactive" states since in practice some of the states can get pretty large or users might create a lot of DOM so I'd like to keep the DOM as light as possible for some states.

I understand that ui-router-extras sticky-states feature is exactly this! And I could use the $state.includes function to target when I want to destroy DOM on some components. However, it seems ui-router-extras does not work with ui-router 1.0.0-beta.3. The author did make a port for the newer ui-router, but the release is in typescript and I am not sure how to compile that into a single js file. See: https://github.com/ui-router/sticky-states/issues/4

Perhaps I need a solution that does not use sticky-states --- any ideas? I was thinking of using a service to cache the scope values, and indeed read some other SO answers to that affect. This means that, per component, I'd need to handle which scope values to cache, etc. This is definitely a possibility, but I am wondering if anyone has any other techniques or knowledge about ui-router such that maybe there is another way to accomplish what I am after: cached controller/scope on transition change.

...

ANSWER

Answered 2017-Mar-28 at 22:23

After reading the author's typescript source code (which was a pleasure, very well-written code) from:

https://github.com/ui-router/sticky-states/blob/master/src/stickyStates.ts

I decided to migrate it to my own service in javascript, which would be compatible with ui.router 1.0.0-beta.3. By the way, ui.router 1.0.0-beta.3 is available at:

https://unpkg.com/angular-ui-router@1.0.0-beta.3/release/angular-ui-router.js

My approach was: because 1.0.0-beta.3 appears to not have the onCreate transition hook, I would decorate the $transitions.create function itself. To do this, I needed to inject a lot of helper functions and the core functionality of sticky states into the decoration. So I made the StickyStatesUtil provider to do this for me.

The migration consists of 2 parts: (1) a module called sticky-states-util, which creates the StickyStatesUtil provider, as well as a useful service for checking if a state/state-name is inactive, and an inactiveEvent, which, if set to a value, will cause $rootScope to broadcast a json map of inactive state-names for anything in the app to consume. If not set, that is skipped. And (2), the actual config block in the angular app that injects $provide and uses that to decorate the $transitions service with a new "create" function.

Since a couple others are in the same spot as me, I made this code available on github:

https://github.com/dsills22/sticky-states-ui-router-1-js

Source https://stackoverflow.com/questions/42914806

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install sticky-states

You can download it from GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: