Release v0.6.5

[marcorosa]

Added

• support for haiku

Fixed

• ui scroll bug when setting weights for heatmap

[github-actions]

This update introduces enhancements across both the backend and frontend of the application. The backend sees the addition of a new model variant supported by Anthropic. Dependencies are upgraded, aligning with minor version bumps in the project's versioning. The frontend improves usability with changes in dialog styling, providing better display scalability.

Walkthrough

• New Feature: Added support for 'anthropic--claude-4.5-haiku' model variant.
• Chore: Updated dependencies and incremented version numbers for backend and frontend.
• Style: Improved CSS styling in the weight dialog to enhance user experience on the frontend.
• Refactor: Simplified logic for reloading heatmap data by removing conditional checks post dialog closure.

_{Model: gpt-4o-2024-08-06 | Prompt Tokens: 1233 | Completion Tokens: 147}

[github-actions]

Here's a collaborative code review powered by AI assistance. These suggestions offer potential improvements and insights to consider for your project. Please treat AI recommendations as helpful guidance rather than definitive solutions. Your expertise and judgment remain the most important factors in making the right decisions for your code. Use what resonates with you and feel confident in your choices as the developer.

---

Always critique what AI says. Do not let AI replace YOUR I.
_{Model: claude-sonnet-4-20250514 | Prompt Tokens: 2445 | Completion Tokens: 907}

[github-actions]

The logic change to always reload heatmap data regardless of the dialog result may not be optimal. Consider reloading only when changes were actually made to avoid unnecessary API calls and improve performance.

dialogRef.afterClosed().subscribe(result => {
  if (result === true) {
    // Only reload when weights were successfully updated
    this.loadHeatmapData();
  }
});

Alternatively, if you need to handle both success and cancellation scenarios differently, use a more descriptive result object:

dialogRef.afterClosed().subscribe(result => {
  if (result?.updated === true) {
    this.loadHeatmapData();
  }
});

[github-actions]

The CSS structure could be improved for better maintainability. Consider using more semantic naming and consistent spacing units.

.dialog-container {
  padding: 1rem;
  max-height: 90vh;
}

.weight-form-container {
  width: 60%;
  margin: 0 auto;
  padding-top: 0.625rem;
  overflow-y: auto;
}

.weight-form-section {
  width: 90%;
  margin: 0 auto;
  max-height: 70vh;
  overflow-y: auto; /* Add this for consistency */
}

Also consider using CSS custom properties for repeated values like widths and margins to improve maintainability.

[github-actions]

The HTML structure has improved with better semantic containers, but consider adding accessibility attributes and handling potential performance issues with large lists.

<div class="weight-form-container">
    <div class="weight-form-section" role="form" aria-label="Attack weights configuration">
        <form>
            <div *ngFor="let attack of attackNames; trackBy: trackByAttackName">
                <mat-form-field appearance="outline" class="form-field">
                    <mat-label>{{ attack }}</mat-label>
                    <input 
                        matInput 
                        type="number" 
                        min="0" 
                        step="1" 
                        [(ngModel)]="currentWeights[attack]"
                        [name]="attack"
                        [attr.aria-label]="'Weight for ' + attack" />
                </mat-form-field>
            </div>
        </form>
    </div>
</div>

Add a trackBy function to the component for better performance:

trackByAttackName(index: number, attack: string): string {
  return attack;
}