* fix after rebase * new release strategy for ng next Signed-off-by: eromano <eugenioromano16@gmail.com> * peer dep Signed-off-by: eromano <eugenioromano16@gmail.com> * Angular 14 fix unit test and storybook Signed-off-by: eromano <eugenioromano16@gmail.com> fix after rebase Signed-off-by: eromano <eugenioromano16@gmail.com> update pkg.json Signed-off-by: eromano <eugenioromano16@gmail.com> missing dep Signed-off-by: eromano <eugenioromano16@gmail.com> Fix mistake and missing code Dream....build only affected libs Add utility run commands * Use nx command to run affected tests * Fix nx test core fix content tests Run unit with watch false core test fixes reduce test warnings Fix process cloud unit Fix adf unit test Fix lint process cloud Disable lint next line Use right core path Fix insights unit fix linting insights Fix process-services unit fix the extensions test report fix test warnings Fix content unit Fix bunch of content unit * Produce an adf alpha of 14 * hopefully fixing the content * Push back the npm publish * Remove flaky unit * Fix linting * Make the branch as root * Get rid of angualar13 * Remove the travis depth * Fixing version for npm * Enabling cache for unit and build * Fix scss for core and paths Copy i18 and asset by using ng-packager Export the theming alias and fix path Use ng-package to copy assets process-services-cloud Use ng-package to copy assets process-services Use ng-package to copy assets content-services Use ng-package to copy assets insights * feat: fix api secondary entry point * fix storybook rebase * Move dist under dist/libs from lib/dist * Fix the webstyle * Use only necessary nrwl deps and improve lint * Fix unit for libs * Convert lint.sh to targets - improve performance * Use latest of angular * Align alfresco-js-api Signed-off-by: eromano <eugenioromano16@gmail.com> Co-authored-by: eromano <eugenioromano16@gmail.com> Co-authored-by: Mikolaj Serwicki <mikolaj.serwicki@hyland.com> Co-authored-by: Tomasz <tomasz.gnyp@hyland.com>
2.6 KiB
Title, Added, Status, Last reviewed
Title | Added | Status | Last reviewed |
---|---|---|---|
Storage service | v2.0.0 | Active | 2018-11-14 |
Storage service
Stores items in the form of key-value pairs.
Class members
Methods
- clear()
Removes all currently stored items. - getItem(key:
string
):string|null
Gets an item.- key:
string
- Key to identify the item - Returns
string|null
- The item (if any) retrieved by the key
- key:
- hasItem(key:
string
):boolean
Is any item currently stored underkey
?- key:
string
- Key identifying item to check - Returns
boolean
- True if key retrieves an item, false otherwise
- key:
- removeItem(key:
string
)
Removes a single item.- key:
string
- Key to identify the item
- key:
- setItem(key:
string
, data:string
)
Stores an item- key:
string
- Key to identify the item - data:
string
- Data to store
- key:
Details
The service will check to see if web storage is available on the browser. If it is available then the service will use it to store the key-value items persistently. Web storage can be used in a similar way to cookies but with a much higher size limit (several MB for web storage compared to a few KB for cookies). However, cookies are more widely supported by browsers and can be set to expire after a certain date.
If local storage is not available then non-persistent memory storage within the app is used instead.
Storage specific to an ADF app
If you are using multiple ADF apps, you might want to set the following configuration so that the apps have specific storages and are independent of others when setting and getting data from the local storage.
In order to achieve this, you will only need to set your app identifier under the storagePrefix
property of the app in your app.config.json
file.
"application": {
"storagePrefix": "ADF_Identifier",
"name": "Your app name",
"copyright": "Your copyright message"
}
Important note This identifier must be unique to the app to guarantee that it has its own storage.
SSO storagePrefix related scenario
The storagePrefix can allow you to login with multiple user in the same browser only if: - Or You don't use the implicit flow - Or You use implicit flow you use different AIMS instances for any app