fix: index.html page example

[horochx]

• fix curl example
• fix server name

Description

Motivation

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Refactoring (no functional changes)

How Has This Been Tested?

• Unit Tests
• Integration Tests
• Manual Testing

Screenshots (if applicable)

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

Related Issues

[matter-code-review]

Summary By MatterAI

🔄 What Changed

This PR fixes formatting and layout issues in the index.html page example. The changes include proper indentation, consistent spacing, and improved code structure throughout the HTML file. Key areas improved include API configuration examples, animation keyframes, UI event handlers, and curl command formatting.

🔍 Impact of the Change

The changes improve code readability and maintainability without altering functionality. The fixes ensure consistent formatting across the codebase, making it easier for developers to understand and modify the code in the future.

📁 Total Files Changed

1 file changed with 58 additions and 58 deletions (116 total changes).

🧪 Test Added

N/A - This PR focuses on HTML formatting improvements which don't require additional tests.

🔒 Security Vulnerabilities

N/A - No security vulnerabilities were addressed in this PR.

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Refactoring (no functional changes)

How Has This Been Tested?

• Manual Testing

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

Tip

Quality Recommendations

1. Add proper input validation for API keys and other user inputs to prevent security issues

2. Implement CSRF protection for the form submissions

3. Add error handling for the EventSource connection failures with exponential backoff

4. Consider adding aria-labels to improve accessibility for interactive elements

5. Add loading indicators during API calls to improve user experience

Sequence Diagram

sequenceDiagram
    participant User
    participant Browser
    participant Gateway
    participant LLMProviders
    
    User->>Browser: Loads index.html page
    Browser->>User: Displays UI with provider options
    
    Note over Browser: User can configure different routing strategies
    
    alt Load Balancing Strategy
        User->>Browser: Configures load balancing
        Browser->>Gateway: curl ${location.origin}/v1/chat/completions with load balance config
        Gateway->>LLMProviders: Routes requests to OpenAI (70%) and Anthropic (30%)
    else Fallback Strategy
        User->>Browser: Configures fallback
        Browser->>Gateway: curl ${location.origin}/v1/chat/completions with fallback config
        Gateway->>LLMProviders: Tries OpenAI first, falls back to Anthropic if needed
    else Auto-Retry Strategy
        User->>Browser: Configures retry and timeout
        Browser->>Gateway: curl ${location.origin}/v1/chat/completions with retry config
        Gateway->>LLMProviders: Retries on status codes 429, 502, 503, 504
    end
    
    LLMProviders->>Gateway: Response
    Gateway->>Browser: Response
    Browser->>User: Displays result
    
    Note over Browser: UI includes log viewing functionality
    Browser->>Gateway: Connects to log stream via EventSource
    Gateway->>Browser: Sends log events (connected, log, heartbeat)
    Browser->>User: Displays logs in table with details view

Loading

[matter-code-review]

I've reviewed the HTML formatting changes in this PR. The changes look good overall, improving code readability with consistent spacing and indentation. I have a few suggestions for further improvements below.

[narengogi]

Screenshots (if applicable)

Hey @horochx, I see two pairs of double quotes in the model field here, is this intended?

[horochx]

Screenshots (if applicable)

Hey @horochx, I see two pairs of double quotes in the model field here, is this intended?

My apologies if it seemed intentional. I didn't modify this section; I only corrected the host address and a JSON formatting error. This part already had double quotes.