mirror of
https://github.com/Alfresco/alfresco-content-app.git
synced 2025-05-12 17:04:46 +00:00
ec18f6b9cb
* [ACS-4130] Added autocomplete for 'Has Category' option in manage rules * [ACS-4130] Added loading spinner and 'No options found' template for Has Category rule condition. Options are now fetched as soon as user selected 'Has Category' option * [ACS-4130] Added code to fetch category name when viewing/editing existing rule with has category option selected * [ACS-4130] Resolved issues related to editing existing rules with 'Has Category' condition * [ACS-4130] Added safety checks and minor code refactoring * [ACS-4130] Added unit tests for new autocomplete functionality * [ACS-4130] Added feature to auto select first option from autocomplete dropdown when user focuses out of autocomplete input field * [ACS-4130] Minor code refactoring. Moved constants from global scope to local scope * [ACS-4130] Moved mock data to conditions.mock.ts. Removed redundant return type * [ACS-4130] Resolved PR review comments - AutoCompleteOption is now an interface. Changed occurences of autocomplete with auto-complete. Removed/Added types * [ACS-4130] Resolved PR review comments - AutoCompleteOption is now built using a single common helper method * [ACS-4130] Added missed types
Alfresco Content Application
Please refer to the public documentation for more details
Requirements
| Name | Version |
|---|---|
| Node.js | 18.x |
| Npm | 9.x |
Compatibility
| ACA | ADF | ACS | Node | Angular |
|---|---|---|---|---|
| 4.2 | 6.3 | 23.1.0-M4 | 18.x | 14.x |
| 4.1 | 6.2 | 7.4 | 18.x | 14.x |
| 4.0 | 6.1 | 7.4 | 14.x | 14.x |
| 3.1 | 5.1 | 7.3 | ||
| 3.0 | 5.0 | 7.3 |
See https://angular.io/guide/versions for more details on Angular and Node.js compatibility
Running
Create an .env file in the project root folder with the following content
BASE_URL="<URL>"
Where <URL> is the address of the ACS.
Run the following commands:
npm install
npm start
Unit Tests
Use following command to test the projects:
nx test <project>
Code Coverage
The projects are already configured to produce code coverage reports in console and HTML output.
You can view HTML reports in the ./coverage/<project> folder.
When working with unit testing and code coverage improvement, you can run unit tests in the "live reload" mode:
nx test <project> -- --watch
Upon changing unit tests code, you can track the coverage results either in the console output, or by reloading the HTML report in the browser.