
Security News
Open Source Maintainers Demand Ability to Block Copilot-Generated Issues and PRs
Open source maintainers are urging GitHub to let them block Copilot from submitting AI-generated issues and pull requests to their repositories.
Angular decorators to automagically keep variables in HTML5 LocalStorage, SessionStorage, cookies; injectable services for managing and listening to data changes and a bit more.
This library adds decorators that make it super easy to automagically save and restore variables using HTML5's localStorage
and sessionStorage
. It also provides Angular-Injectable Session- and LocalStorageService.
@LocalStorage()
- to save variable in HTML5 localStorage@SessionStorage()
- to save variable in HTML5 sessionStorage@CookieStorage()
- to save variable as a cookie@SharedStorage()
- to keep variable in temporary memory that can be shared across classes@TempStorage()
- alias for SharedStorage
LocalStorageService
, SessionStorageService
, CookiesStorageService
and SharedStorageService
(read more here)angular2-localstorage
(seamless migration)migrateKey
decorator config option.forRoot()
and .forChild()
methods for future use@LocalStorage() @CookieStorage() variable: any;
CookieStorage
(decorator closer to variable) has higher priority, hence the value will be read from cookies only. The cookie value will be saved in localStorage
regardless of its content to keep consistency.WebStorageService.clear('all')
- now will remove everything except ngx-store
's config (stored in localStorage
)WEBSTORAGE_CONFIG
@SharedStorage
has now alias @TempStorage
Just run: ng add ngx-store
. Done!
npm i ngx-store --save
app.module.ts
:
import { NgModule } from '@angular/core';
import { WebStorageModule } from 'ngx-store';
@NgModule({
imports: [
WebStorageModule.forRoot(),
],
})
export class AppModule {}
Things you should take into consideration while configuring this module:
.save()
method to easily force save of made changes (configurable by mutateObjects
)Array
methods that change array object's value can be disabled (configurable by mutateObjects
)''
), however we recommend to use it, as it helps avoid conflicts with other libraries (configurable by prefix
)'all'
- completely clears current Storage'prefix'
- removes all variables prefixed by ngx-store'decorators'
- removes only variables created by decorating functions (useful when not using prefix)
Default behaviour is specified by setting clearType
, but it's possible to pass this parameter directly into service clear()
method.cookiesScope
can be found in this commentAs this project uses decorating functions, it is important to provide custom configuration in global variable named NGXSTORE_CONFIG
before Angular application load. Here are some ways to do it:
<script>
in index.html
(before Angular sources)
<script>
var NGXSTORE_CONFIG = {
prefix: 'ngx_', // default: 'ngx_'
clearType: 'prefix', // default: 'prefix'
mutateObjects: true, // default: true
debugMode: false, // you can enable debug logs if you ever meet any bug to localize its source
cookiesScope: '', // what you pass here will prepend base domain e.g. "." => .domain.com (all subdomains)
cookiesCheckInterval: 0, // number in ms describing how often cookies should be checked for changes, 0 = disabled
previousPrefix: 'angular2ws_', // you have to set it only if you were using custom prefix in old version ('angular2ws_' is a default value)
};
</script>
webpack.js
file this way:
plugins: [
new webpack.DefinePlugin({
NGXSTORE_CONFIG: JSON.stringify({
prefix: '', // etc
})
}),
]
Decorating functions can take config object with the following fields:
key: string
- key under the variable will be stored, default key is the variable namemutate: boolean
- enable or disable object mutation for instance, default depends on global configexpires: Date
- for @CookieStorage()
only, specifies expiration date, null = lifetime cookiemigrateKey: string
- previously used key from which the value will be transferred to the current key
, the old key will be cleared afterwardsPretty easy to use decorators. Here is where the real magic happens.
import { CookieStorage, LocalStorage, SessionStorage } from 'ngx-store';
export class MySuperComponent {
// it will be stored under ${prefix}viewCounts name
@LocalStorage() viewCounts: number = 0;
// this under name: ${prefix}differentLocalStorageKey
@LocalStorage('differentLocalStorageKey') userName: string = '';
// it will be stored under ${prefix}itWillBeRemovedAfterBrowserClose in session storage
@SessionStorage({key: 'itWillBeRemovedAfterBrowserClose'}) previousUserNames: Array<string> = [];
// it will be read from cookie 'user_id' (can be shared with backend) and saved to localStorage and cookies after change
@LocalStorage() @CookieStorage({prefix: '', key: 'user_id'}) userId: string = '';
// it will be stored in a cookie named ${prefix}user_workspaces for 24 hours
@CookieStorage({key: 'user_workspaces', expires: new Date(new Date().getTime() + 24 * 60 * 60 * 1000)}) userWorkspaces = [];
// the value will be transferred from localStorage's "location" key
@LocalStorage({key: 'myLocation', migrateKey: 'location'}) myLocation: string = '';
constructor() {
this.viewCounts++;
this.userName = 'some name stored in localstorage';
this.previousUserNames.push(this.userName);
for (let userName of this.previousUserNames) {
console.log(userName);
}
this.previousUserNames.map(userName => userName.split('').reverse().join(''));
}
}
Sharing variables across classes: Decorated variables can be easily shared across different classes, e.g. Angular Components (also after their destruction) without need to create new service for this purpose.
import { LocalStorage, SharedStorage } from 'ngx-store';
export class HomeComponent {
@SharedStorage() title: string = 'Homepage'; // it will be kept in temp memory until app reload
@LocalStorage() userNote: string = 'Leave your note here'; // it will be read from and saved to localStorage
constructor() {
setTimeout(() => {
console.log('userNote:', this.userNote); // it should be changed after user's visit to NestedComponent
}, 5000);
}
}
export class NestedComponent {
@SharedStorage('title') homeTitle: string = '';
@LocalStorage() protected userNote: string = '';
constructor() {
console.log('homeTitle:', this.homeTitle); // should print 'Homepage'
console.log('userNote:', this.userNote); // should print userNote set in HomeComponent
this.userNote = "You've visited NestedComponent!";
}
}
Force save changes: If you need to modify stored object by not a direct assignment, then you can take advantage of .save()
method to force save made changes. Example:
import { CookieStorage, LocalStorage, SessionStorage, WebstorableArray } from 'ngx-store';
export class MySuperComponent {
@LocalStorage() someObject: any = { c: 3 };
@SessionStorage() arrayOfSomethings: WebstorableArray<number> = <any>[0,1,2,3,4];
@CookieStorage({ mutate: false }) someCookie: {version?: number, content?: string} = {};
constructor() {
this.someObject.a = 1;
this.someObject['b'] = 2;
delete this.someObject['c'];
for (let i = 0; i < this.arrayOfSomethings.length; i++) {
this.arrayOfSomethings[i] += i;
}
this.someCookie.version++;
this.someCookie.content = 'please save me';
// upper changes won't be saved without the lines below
this.someObject.save();
this.arrayOfSomethings.save();
this.someCookie = this.someCookie; // it looks weird, but also will do the job even without object mutation
}
}
Limited lifecycle classes in AoT compilation: There is a special case when Service or Component in your application containing decorated variable is being destroyed:
import { OnDestroy } from '@angular/core';
import { LocalStorage } from 'ngx-store';
export class SomeService implements OnDestroy { // implement the interface
@LocalStorage() destroyedVariable: any = {};
ngOnDestroy() {} // event empty method is needed to allow ngx-store handle class destruction
}
Use the services to manage your data:
import { CookiesStorageService, LocalStorageService, SessionStorageService, SharedStorageService } from 'ngx-store';
export class MyService {
constructor(
localStorageService: LocalStorageService,
sessionStorageService: SessionStorageService,
cookiesStorageService: CookiesStorageService,
sharedStorageService: SharedStorageService,
) {
console.log('all cookies:');
cookiesStorageService.utility.forEach((value, key) => console.log(key + '=', value));
}
public saveSomeData(object: Object, array: Array<any>) {
this.localStorageService.set('someObject', object);
this.sessionStorageService.set('someArray', array);
this.localStorageService.keys.forEach((key) => {
console.log(key + ' =', this.localStorageService.get(key));
});
}
public clearSomeData(): void {
this.localStorageService.clear('decorators'); // removes only variables created by decorating functions
this.localStorageService.clear('prefix'); // removes variables starting with set prefix (including decorators)
this.sessionStorageService.clear('all'); // removes all session storage data
}
}
Note: Always define default value at the property you are using decorator.
Note: Never use for-in
loop on decorated Arrays without filtering by .hasOwnProperty()
.
Note: Please don't ngx-store circular structures as this library uses JSON.stringify to encode data before saving.
Note: When you change prefix from '' (empty string) old values won't be removed automatically to avoid deleting necessary data. You should handle it manually or set clearType to 'all' for some time.
Contributions are welcome!
FAQs
Angular decorators to automagically keep variables in HTML5 LocalStorage, SessionStorage, cookies; injectable services for managing and listening to data changes and a bit more.
The npm package ngx-store receives a total of 1,966 weekly downloads. As such, ngx-store popularity was classified as popular.
We found that ngx-store demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Open source maintainers are urging GitHub to let them block Copilot from submitting AI-generated issues and pull requests to their repositories.
Research
Security News
Malicious Koishi plugin silently exfiltrates messages with hex strings to a hardcoded QQ account, exposing secrets in chatbots across platforms.
Research
Security News
Malicious PyPI checkers validate stolen emails against TikTok and Instagram APIs, enabling targeted account attacks and dark web credential sales.