Menü
ReDBox uses embedded Angular applications within EJS views instead of a single SPA. Each feature is often its own Angular project.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Angular services in ReDBox typically extend `HttpClientService` to handle base URLs, configuration, and CSRF protection.
ReDBox controllers live in `@researchdatabox/redbox-core` and are surfaced to Sails.js through generated shims.
Create detailed feature designs, implementation plans, and task lists for ReDBox/Redbox features that use Waterline models, services, webservice (REST) controllers, ajax controllers, embedded Angular apps, views, and navigation config. Use when asked to design/plan a feature or produce a task list for this stack, especially when explicit sections, non-SPA Angular patterns, and interleaved tests are required.
Review completed ReDBox feature implementations against a growing ruleset and emit structured issues for agent remediation.
Build or update ReDBox form field components end-to-end across Angular form rendering and sails-ng-common config typing/visitor infrastructure. Use when creating a new form component class/model, adding component config properties, wiring component dictionaries, handling config migration/template extraction, or adding form-component tests.
ReDBox uses a JSON-based DSL for configuring record forms, workflows, and record types.
Basierend auf der SOC-Berufsklassifikation
| name | Redbox Angular Apps |
| description | ReDBox uses embedded Angular applications within EJS views instead of a single SPA. Each feature is often its own Angular project. |
ReDBox uses embedded Angular applications within EJS views instead of a single SPA. Each feature is often its own Angular project.
angular/projects/researchdatabox/<app-name>/assets/angular/<app-name>/browser/views/default/default/admin/<app-name>.ejsUse the redbox-dev-tools CLI generator generate_angular_app:
name: App name as an argument (lowercase).--ejs-view <view>: EJS view name.--auth <roles>: Roles for page access.@angular-devkit/build-angular:application.CacheService.getNgAppFileHash(appName, type, prefix) for hashed asset names.RenderViewController.render with the view specified in locals.New projects must be added to angular.json with appropriate outputPath and baseHref.
Example outputPath: ../assets/angular/<name>
To run tests for a specific Angular app:
ng test <app-name>npm test -- <app-name>If running inside a container as root (e.g. Docker), you must use the --browsers=ChromeHeadlessNoSandbox flag:
ng test --browsers=ChromeHeadlessNoSandbox <app-name>
A convenience script is available at support/unit-testing/angular/testDevAngular.sh which handles the browser flags logic automatically.