Files
alfresco-ng2-components/ng2-components
Denys Vuika 5c401007f2 user-info fixes and performance improvements (#1171)
* #1167 document-list improvements

- allow setting custom root path
- document-list module now re-exports datatable module (no need
importing it separately if document-list is already used)
- documentation updates and fixes

* readme updates and unit test

* user-info fixes and performance improvements

- setup live reloads for user-info (demo shell)
- optimise user-info template (single *ngIf, [mdl] directive for
‘user-profile-lists’ instead of CPU-hungry `ngAfterViewChecked`)
2016-11-29 13:26:41 +00:00
..
2016-11-25 19:09:08 +00:00
2016-11-25 19:09:08 +00:00
2016-11-25 19:09:08 +00:00
2016-11-25 19:09:08 +00:00
2016-11-25 19:09:08 +00:00
2016-11-25 19:09:08 +00:00
2016-10-04 14:25:41 +01:00

Alfresco Angular 2 Components

travis
    Status travis
    Status Coverage Status license alfresco component angular 2 typescript node version

Base components

  • Material Design elements
  • Context Menu component

ECM components

BPM components

You can browse all the components at the following address:

http://devproducts.alfresco.com/

How to test a change to a generic component in its own demo

Let's suppose that for some reason you have changed a component and you want to test this changes. The example is based on the ng2-alfresco-login component, but you can use the same steps for any component.

  1. Move inside the component folder and link it.

cd ng2-alfresco-login
npm link

  1. Build the component with the watcher enabled.

npm run build:w

  1. From another terminal move inside the demo sub folder and link the component to the local node_modules folder.

cd demo
npm link ng2-alfresco-login

  1. Start the demo project.

npm run start