Avoid aliases for new routes in PHP

php
Only use route aliases for backward compatibility with renamed or moved routes. Do not add aliases to newly created routes.
Bad:
```php
// Adding an alias to a new route
Route::put('/api/users/{id}')
    ->alias('/api/user/{id}');

Install this rule for wispbit

Add this rule to wispbit and it will run when you open a pull request

Install this rule for Coderabbit

Copy the configuration below and add it to your repository as .coderabbit.yml in your project root.

reviews:
  path_instructions:
    - path: "app/controllers/api/*.php"
      instructions: |
                
        Only use route aliases for backward compatibility with renamed or moved routes. Do not add aliases to newly created routes.
        
        Bad:
        
        ```php
        // Adding an alias to a new route
        Route::put('/api/users/{id}')
            ->alias('/api/user/{id}');
        
        // Another framework example
        $router->map('GET', '/products/{productId}', 'ProductController::show')
            ->alias('product.show.alt');
        ```
        
        Good:
        
        ```php
        // New route without an alias
        Route::put('/api/users/{id}');
        ```

Install this rule for Greptile

Greptile rules can be added through the web interface. Please see this documentation for details on how to add custom rules and context.

Only use route aliases for backward compatibility with renamed or moved routes. Do not add aliases to newly created routes.
Bad:
```php
// Adding an alias to a new route
Route::put('/api/users/{id}')
    ->alias('/api/user/{id}');
// Another framework example
$router->map('GET', '/products/{productId}', 'ProductController::show')
    ->alias('product.show.alt');
```
Good:
```php
// New route without an alias
Route::put('/api/users/{id}');
```

File Path Patterns:

app/controllers/api/*.php

Install this rule for GitHub Copilot

Copilot instructions can be added through the interface. See the documentation for details on how to create coding guidelines.

Only use route aliases for backward compatibility with renamed or moved routes. Do not add aliases to newly created routes.
Bad:
```php
// Adding an alias to a new route
Route::put('/api/users/{id}')
    ->alias('/api/user/{id}');
// Another framework example
$router->map('GET', '/products/{productId}', 'ProductController::show')
    ->alias('product.show.alt');
```
Good:
```php
// New route without an alias
Route::put('/api/users/{id}');
```

File Path Patterns:

app/controllers/api/*.php

Install this rule for Graphite Diamond

Diamond custom rules can be added through the interface. See the documentation for details on how to create custom rules.

Only use route aliases for backward compatibility with renamed or moved routes. Do not add aliases to newly created routes.
Bad:
```php
// Adding an alias to a new route
Route::put('/api/users/{id}')
    ->alias('/api/user/{id}');
// Another framework example
$router->map('GET', '/products/{productId}', 'ProductController::show')
    ->alias('product.show.alt');
```
Good:
```php
// New route without an alias
Route::put('/api/users/{id}');
```

File Path Patterns:

app/controllers/api/*.php

Use with Cline

Copy the rule below and ask Cline to review your code using this rule

Only use route aliases for backward compatibility with renamed or moved routes. Do not add aliases to newly created routes.
Bad:
```php
// Adding an alias to a new route
Route::put('/api/users/{id}')
    ->alias('/api/user/{id}');
// Another framework example
$router->map('GET', '/products/{productId}', 'ProductController::show')
    ->alias('product.show.alt');
```
Good:
```php
// New route without an alias
Route::put('/api/users/{id}');
```

Use with OpenAI Codex

Copy the rule below and ask OpenAI Codex to review your code using this rule

Only use route aliases for backward compatibility with renamed or moved routes. Do not add aliases to newly created routes.
Bad:
```php
// Adding an alias to a new route
Route::put('/api/users/{id}')
    ->alias('/api/user/{id}');
// Another framework example
$router->map('GET', '/products/{productId}', 'ProductController::show')
    ->alias('product.show.alt');
```
Good:
```php
// New route without an alias
Route::put('/api/users/{id}');
```

Use with Cursor

Copy the rule below and ask Cursor to review your code using this rule

Only use route aliases for backward compatibility with renamed or moved routes. Do not add aliases to newly created routes.
Bad:
```php
// Adding an alias to a new route
Route::put('/api/users/{id}')
    ->alias('/api/user/{id}');
// Another framework example
$router->map('GET', '/products/{productId}', 'ProductController::show')
    ->alias('product.show.alt');
```
Good:
```php
// New route without an alias
Route::put('/api/users/{id}');
```

Use with Claude Code

Copy the rule below and ask Claude Code to review your code using this rule

Only use route aliases for backward compatibility with renamed or moved routes. Do not add aliases to newly created routes.
Bad:
```php
// Adding an alias to a new route
Route::put('/api/users/{id}')
    ->alias('/api/user/{id}');
// Another framework example
$router->map('GET', '/products/{productId}', 'ProductController::show')
    ->alias('product.show.alt');
```
Good:
```php
// New route without an alias
Route::put('/api/users/{id}');
```

Install this rule for Windsurf

To set up rules for Windsurf Reviews, please see this documentation 

Only use route aliases for backward compatibility with renamed or moved routes. Do not add aliases to newly created routes.
Bad:
```php
// Adding an alias to a new route
Route::put('/api/users/{id}')
    ->alias('/api/user/{id}');
// Another framework example
$router->map('GET', '/products/{productId}', 'ProductController::show')
    ->alias('product.show.alt');
```
Good:
```php
// New route without an alias
Route::put('/api/users/{id}');
```