mirror of
https://github.com/Alfresco/alfresco-ng2-components.git
synced 2025-05-19 17:14:57 +00:00
6da0eaba37
* fix sourcemap fix relative path and pre publish build change travis wait all test run build and remove unused cpx * global test task modify publish script to accept options * appveyor run * different approach single test run * make it work the analytics test modify start demo shell script to use a different registry * sourcemap demo shell working * update readme and add install after any clean add registry option in start.sh script add develop and normal mode in demo shell add -d option in start.sh to point to the local components add -c option in build script to point to the local components
Alfresco Angular 2 Components
Base components
- Material Design elements
- Context Menu component
ECM components
- DataTable
- DocumentList
- Login
- Search
- Social
- Tag list and controls
- User Info
- Upload
- Viewer
- Webscript Viewer
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.
- Move inside the component folder and link it.
cd ng2-alfresco-login
npm link
- Build the component with the watcher enabled.
npm run build:w
- 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
- Start the demo project.
npm run start