AI Prompts for Identify Export Mismatch Issues

Please provide the exact error message from the console that indicates an export mismatch related to the [COMPONENT OR FUNCTION NAME]. Include details about the context in which the error occurs, such as the file name and line number, and explain why this error is happening. Format your response as a structured report with sections for the error message, context, and explanation.

Please provide the import statement from the file where the error occurs. I need to analyze how it references the exported component or function. Additionally, include the context of the file structure and any relevant code snippets that may help in diagnosing the issue, so I can give you a more accurate assessment.

Please confirm your understanding of the required export type for the component in question. Provide a detailed explanation of the export type you believe is necessary, including any relevant examples or context that support your understanding. This will help clarify any potential misinterpretations before you retry the export.

Please provide a detailed comparison of the expected export type versus the actual export type used in the code for the use-case of [USE-CASE NAME]. Clearly outline the expected behavior of the component, including any relevant context or specifications. Format your response in a table with columns for "Expected Export Type," "Actual Export Type," and "Description of Expected Behavior.

Identify the specific rule or convention regarding exports that has been violated in the following code snippet: [CODE SNIPPET]. Please quote the relevant clause or guideline from the documentation and explain how it applies to this instance. Additionally, suggest a corrected version of the export that adheres to the identified rule.

Please review the export statement in the file [FILE] at line [LINE]. It is currently set as a default export. Change it to a named export by replacing the current export, which is: [PASTE CURRENT EXPORT], with the following corrected version: [PASTE NEW EXPORT]. Provide a brief explanation of why this change is necessary and how it improves the code structure.

Rewrite the import statement in the file located at [FILE] on line [LINE]. It is currently referencing a default export incorrectly. Please change it to correctly import the named export using the following format: [PASTE NEW IMPORT]. Provide the corrected import statement as the output.

In [FILE] at line [LINE], please revert the export type to match the original specification. The original export was: [PASTE ORIGINAL EXPORT]. Make sure that only the export type is modified, and provide a brief explanation of why this change is necessary for maintaining compatibility with the existing codebase.

Please review the export statements in [FILE] and ensure they all follow the named export format. Identify any export statements that do not comply with this structure and provide a detailed explanation of the issues found. Additionally, suggest specific corrections for each non-compliant export statement to align them with the required format.

Please verify the import dependencies in the file [FILE]. Check all dependencies to ensure they are correctly importing the named exports. Provide a detailed list of any imports that need to be corrected, along with a brief explanation of the necessary changes for each one.

Please run the application test again and monitor the console for any remaining export-related errors. Document any errors that appear, and confirm whether the initial issue has been fully resolved. Provide a summary of your findings, including any errors encountered and the steps taken to verify the resolution.

Display the differences in the export statements of the file [FILE]. Provide a clear comparison that highlights what changes were made, including any additions, deletions, or modifications to the export patterns. Ensure the output is formatted in a way that allows for easy identification of the specific changes and their implications for the overall code functionality.

Reproduce the original scenario that caused the export error in the application. Please provide a detailed step-by-step account of how to replicate the issue, including any specific inputs or configurations used. After reproducing the scenario, confirm whether the application now functions correctly without any errors and summarize any changes made to resolve the issue.

Please test the component related to the export issue for any edge cases that may arise. Specifically, identify and document at least three edge cases that could potentially trigger errors. After testing, provide a summary of the results, including whether any errors were encountered and recommendations for further improvements if necessary.

Please verify the output state of [FILE] to ensure it correctly reflects the expected behavior following the export fix. Describe any discrepancies you observe and suggest potential reasons for these issues. Additionally, provide a summary of the changes made to the export pattern and how they should impact the output.

Before deployment, please check the export types in [PROJECT NAME] for consistency. Ensure that all exports are either named or default according to the project's conventions. If you identify any mismatches, provide a detailed report of the inconsistencies and recommend actions to rectify them before proceeding with the deployment.

Generate a project convention message regarding export patterns for components. The message should clearly state: 'All components must use named exports unless specified otherwise. Review your exports regularly to ensure compliance.' Additionally, provide a brief explanation of why adhering to this convention is important for maintainability and collaboration within the team.

Please create a code comment guard in [FILE] that includes the following text: 'Ensure this component uses a named export. If this is a default export, it must be changed to a named export before merging.' Make sure the comment is placed at the top of the file and is formatted correctly for clarity. Additionally, explain why using named exports is beneficial for maintainability and readability in the codebase.

Please create a self-check request for an agent that verifies export types before any changes are made. The agent should check if the export type matches the expected type, and if there is a mismatch, it should alert the user with a clear message to review the export statement. Format the output to include the export type, expected type, and the alert message for the user.

Create a conversation-starter template for developers that emphasizes the importance of verifying export types before making changes to any component. The template should include a prompt asking: 'Before making changes, please confirm the expected export type for this component. Is it a named export or a default export?' Additionally, provide a brief explanation of why this verification is crucial for maintaining code integrity and preventing errors.