Mario Romano 11894a9769 Dev mromano improveprocess (#1334)
* fix overload activiti

* fix reload tasklist

* fix process variables

* fix default filter

* improve process list

* fix tests process

* fix tests

* Fix test for form

* fix tests

* fix tests

* #fix activiti bug

* #fix activiti bug (reverted from commit c966395ed1087e1dedaf0af0923a89ba99d6ab9f)

* fix tests

* #fix header test bug

* fix tests

* fix process

* fix tests
2016-12-20 09:37:56 +00:00
..
2016-12-15 01:07:08 +00:00
2016-12-15 01:07:08 +00:00
2016-12-15 01:07:08 +00:00
2016-12-15 01:07:08 +00: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