Maurizio Vitale 1fa81962a0
👽 Angular 14 rebase 👽 (#7769)
* 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>
2022-08-25 10:50:30 +01:00
..
2022-08-25 10:50:30 +01:00
2022-08-25 10:50:30 +01:00
2019-06-11 19:44:17 +01:00
2022-08-25 10:50:30 +01:00
2021-05-20 17:14:42 +01:00
2020-05-04 17:46:22 +01:00
2021-05-20 09:50:30 +01:00
2021-03-23 17:12:55 +00:00

Running a demo project

The Alfresco application development framework comes with a demo project that you can run to get a feel of what's available.

  • Start by navigating into the app development framework source folder, and then the scripts folder:
 cd alfresco-ng2-components
 cd scripts

npm-check-bundles.sh check the bundles in the package npm are present

Options

Option Description
-h or --help show the help
-r or --registry against which register you want to do this check
-v or --version the version of the components to check

npm-add-pkg.sh

npm-add-pkg.sh check the bundles in the package npm are present

Add a package across all the pacakge json in the project

Options

Option Description
-h or --help show the help
--save save it in dependencies
--save-dev save it in dev dependencies
  • Add a package in the project

Examples

./npm-add-pkg.sh --save-dev NPM_NAME

extract-langs.sh

extract-langs.sh

Extract the i18n files from the repo and create a zip

Options

Option Description
-h or --help show the help
--output or o output folder otherwise will be 18n

Examples

./extract-langs.sh 

test-e2e-bc.sh

test-e2e-bc.sh

This script test that the update from 2.0.0 to 2.x.x is still smooth

Examples

./test-e2e-bc

test-e2e-bc.sh

test-e2e-bc.sh

This script test that the update from 2.0.0 to 2.x.x is still smooth

Examples

./test-e2e-bc

simulate-publish.sh

simulate-publish.sh

This script run a verdaccio server and simulate a publish on it

Examples

./simulate-publish

test-dist.sh

test-dist.sh

This script test the distribution of ADF against the demo shell

Examples

./test-dist

test-e2e-lib.sh

test-e2e-lib.sh

Script to run e2e test

Option Description
-u or --username username to use
-p or --password password to use
-e or --email email user to use
-b or --browser browser run the test in the browsrwer (No headless mode)
-s or --spec spec run a single test file
-dev or --dev run it against local development environment it will deploy on localhost:4200 the current version of your branch
-t or --timeout override the timeout foe the wait utils
-host or --host host against to run the test
-proxy or --proxy proxy Back end URL to use

Examples

./scripts/test-e2e-lib.sh -host adf.domain.com -u admin -p admin -e admin

Run on browser

./scripts/test-e2e-lib.sh -host adf.domain.com -u admin -p admin -e admin --browser

Run a single test

./scripts/test-e2e-lib.sh -host adf.domain.com -u admin -p admin -e admin --spec filenam.e2e.ts

if the test in a subfolder in e2e you need to add the subfolder in the path:

./scripts/test-e2e-lib.sh -host adf.domain.com -u admin -p admin -e admin --spec ./core/filenam.e2e.ts

Use a different backend

./scripts/test-e2e-lib.sh -host localhost:42000 -proxy adf.domain.com  -u admin -p admin -e admin