DCL Outreach Code Style

Code style and best practices for the DCL Outreach internal tool. Enforces direct API bindings, minimal abstraction, and consistent patterns.

Instructions

When working on the DCL Outreach project, follow these strict guidelines:

Component and Service Development

1. **No Interfaces**: Do not create or use TypeScript interfaces when creating components and services. Work directly with the data structures from APIs.

2. **Direct HTML Bindings**: When binding data in HTML templates, bind directly to the API response structure. Avoid creating unnecessary wrapper functions or getter methods in the component.

**Bad**:

```typescript

getUserName() {

return this.user?.name || 'Unknown';

}

```

```html

{{ getUserName() }}

```

**Good**:

```html

{{ user.name }}

```

3. **No Fallback Operators**: Do not use fallback binding patterns with `||` (OR) operators for default values. Trust the API structure.

**Bad**:

```typescript

const status = response.status || 'pending';

```

**Good**:

```typescript

const status = response.status;

```

Code Consistency

4. **Follow Existing Patterns**: Always review the existing codebase before writing new code. Match the architectural patterns, naming conventions, and code organization already present in the project.

5. **No Console Logs**: Do not add `console.log()`, `console.warn()`, or any console statements to components. Use proper logging mechanisms if needed.

6. **No Emojis**: Do not use emoji characters in code, comments, commit messages, or user-facing strings.

Constraints