AI Prompts for Identify Conflicting API Routes

Please quote the exact API endpoint that was generated in your last output which conflicts with an existing route. Identify the specific route in your routing configuration that this endpoint conflicts with, and provide detailed information about both the conflicting endpoint and the existing route, including their paths and any relevant parameters.

Please analyze the following routing configuration file: [ROUTING CONFIGURATION FILE]. Focus specifically on the section where routes are defined. Identify any conflicting routes present, explain why they are conflicting, and suggest possible resolutions for each conflict.

Please explain your interpretation of my last instruction regarding route generation. I want you to clarify any potential misunderstandings that may have contributed to the conflict. Provide a detailed analysis of the instruction, highlighting key points and any areas that could be misinterpreted.

Compare the expected API routes with the actual routes generated in the application. List the expected routes in a clear format, and for each expected route, indicate whether it conflicts with any existing routes. Provide a summary of the conflicts, including the specific routes that are causing issues and any recommendations for resolving these conflicts. Format your response as a table with columns for Expected Route, Actual Route, and Conflict Status.

Identify the specific routing rule or constraint that was violated in the last output regarding the use-case of [USE-CASE]. Please quote the exact clause from the routing guidelines that outlines this rule to clarify the mistake. Additionally, provide a brief explanation of how this violation affects the overall routing process.

Identify the conflicting parameters in the route defined at [FILE]:[LINE]. The original route is: [PASTE]. The conflicting route is: [PASTE]. Please provide a revised version of the original route by reverting only the parameters to resolve the conflict, and explain the changes made.

Rewrite the conflicting route found at [FILE]:[LINE] to eliminate any overlap with existing routes. Ensure the new route follows the format 'GET /api/[NEW_ROUTE]' and clearly specify how it differs from the original 'GET /api/[CONFLICTING_ROUTE]'. Additionally, provide a brief explanation of why this change is necessary to maintain route integrity.

Please modify the route in the file located at [FILE] on line [LINE] to utilize a unique identifier. Change the existing route from 'GET /api/[CONFLICTING_ROUTE]' to 'GET /api/[NEW_UNIQUE_ROUTE]' to ensure there are no conflicts. After making this change, provide a brief explanation of how this adjustment will help prevent routing issues in the application.

Please review the route defined at [FILE]:[LINE] and ensure it adheres to the naming convention of 'GET /api/[RESOURCE]/[ACTION]'. If it does not comply, provide a corrected version of the route that follows this format. Additionally, explain any changes made and the reasoning behind them to ensure clarity and understanding of the convention.

Inspect the imports in [FILE] to identify any dependencies that could be causing route conflicts. Analyze each imported module to ensure they are correctly defined and do not interfere with the routing logic. Provide a detailed report highlighting any issues found and suggest necessary corrections to resolve these conflicts.

Please run a test to verify that all API routes in the [APPLICATION NAME] are functioning correctly. Specifically, check that the routes no longer conflict and return the expected responses. Provide a detailed report that includes the status of each route, any conflicts found, and the expected versus actual responses for each route tested.

Please display the differences between the routing configuration file before and after the changes made to resolve conflicting routes. Include a clear comparison of each line that has been added, removed, or modified, and provide a summary of the key changes that confirm the successful removal of the conflicting routes. Format the output in a side-by-side view for easy comparison.

Replay the original scenario that caused the routing conflict in the application. Verify that the application behaves as expected by checking for any errors related to routing. Provide a detailed report on the application's behavior during the replay, including any discrepancies or issues encountered, and confirm whether the routing conflict has been resolved.

Please analyze the following edge case for the conflicting route in the application: [DESCRIPTION OF EDGE CASE]. Explain how the application currently handles this scenario and identify any potential routing errors that could occur. Additionally, provide recommendations for improving the application's handling of this edge case to ensure it operates smoothly without errors.

Please confirm the state of the routing configuration file after changes have been made. Specifically, check for any remaining conflicts and ensure that all routes are correctly defined. Provide a summary of your findings, including any identified issues and recommendations for resolution, formatted as a report with sections for conflicts, corrections made, and final status.

Before generating routes, verify that no existing routes conflict with new definitions. If a conflict is detected, stop and alert the user before continuing. Please provide this session-opening constraint in a clear and concise format that can be easily implemented in the project.

Create a conversation-starter template that outlines best practices for defining routes in API development. Include key points such as ensuring routes are unique, following a consistent naming pattern like GET /api/[RESOURCE]/[ACTION], and providing examples of common actions for different resources. Format the output as a structured list with headings for each best practice, along with brief explanations for clarity.

Draft a project specification message that clearly outlines the routing conventions for the project. Ensure to include that all API routes must be prefixed with '/api/' and adhere to the naming convention of [RESOURCE]/[ACTION]. Additionally, provide examples of valid routes and explain the importance of maintaining these conventions for consistency and clarity in the API design. Format the output as a structured document with headings for each section.

Please create a detailed guideline for establishing a naming convention for routes to prevent conflicts. The guideline should specify that all routes must be named uniquely, following the pattern: [RESOURCE]_[ACTION]. Include examples of proper naming conventions, potential pitfalls to avoid, and the importance of maintaining this standard to ensure clarity and prevent duplication in the routing system. Format the output as a structured document with headings and bullet points for easy reference.

Please generate a self-check request for the agent to run prior to deployment. The request should include the following instructions: 'Before deployment, ensure that all routes are unique and do not conflict with existing routes. If any conflicts are detected, report them immediately.' Format the output as a clear checklist that the agent can follow.