mirror of
https://github.com/Alfresco/alfresco-ng2-components.git
synced 2025-07-31 17:38:48 +00:00
* coverage single components run fix * remove spec.ts from coverage * make the coverage and the istanbul-instrumenter-loader works only over the console test because a problem on the remapping for the browser test * move tslint on the main folder of any component * remove build:w from readme * stop build tslint error also in spec files * clear karma file from unnecessary files * add set -f for build all script in order to accept * * fix lint problem and failing tests * fix failing test search component * add loader test for viewer * fix tslint error userinfo * --max_old_space_size=2048 remove * fix tslint error uploader unused EventEmitter * remove spec|index|.*mock|.*model|.*event from coverage
Alfresco Angular 2 Components
Base components
- Material Design elements
- Context Menu component
ECM components
- alfresco-webscript-get
- alfresco-pagination
- alfresco-datatable
- alfresco-login
- alfresco-tag-node-actions-list
- alfresco-tag-list
- alfresco-tag-node-list
- alfresco-document-list
- alfresco-document-menu-action
- alfresco-document-list-breadcrumb
- adf-rating
- adf-like
- alfresco-upload-drag-area
- alfresco-upload-button
- alfresco-file-uploading-list
- alfresco-search
- alfresco-search-control
- alfresco-search-autocomplete
- ng2-alfresco-userinfo
BPM components
- activiti-analytics
- activiti-analytics-generator
- activiti-form
- activiti-content
- activiti-start-form
- activiti-process-instance-filters
- activiti-process-instance-list
- activiti-process-instance-details
- activiti-start-process
- activiti-apps
- activiti-tasklist
- activiti-checklist
- adf-task-attachment-list
- activiti-people
- activiti-comments
- activiti-task-header
- activiti-task-details
- activiti-start-task
- activiti-filters
- activiti-people-search
- activiti-process-instance-header
- activiti-process-instance-tasks
- activiti-process-instance-comments
- activiti-process-instance-variables
- activiti-diagram
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