AI Prompts for Adding Null Checks to Prevent Crashes

Please quote the exact error message you received in the console related to null or undefined values. Additionally, identify the specific function or component where this error originated, and provide context about what you were trying to accomplish when the error occurred. Format your response by first stating the error message, followed by the function or component name, and then a brief description of the context.

Please analyze the following code for the specific component that is crashing due to null or undefined values: [CODE SNIPPET]. Identify the locations where these values are not being properly checked and explain how this can lead to crashes. Additionally, suggest appropriate null checks or error handling strategies that could be implemented to prevent these issues.

Please provide your interpretation of the instruction regarding null checks in the context of the use-case "bolt-missing-null-checks." Explain the key points of the instruction, any potential ambiguities, and how these might affect the handling of null values. Format your response as a structured analysis with bullet points summarizing your understanding and any questions you may have for clarification.

Identify the expected behavior when handling null values in the application compared to the actual behavior observed during runtime. Describe in detail what should occur when a null value is encountered, including any error messages, fallback mechanisms, or default values that should be used. Provide a structured comparison in a table format, with columns for "Expected Behavior" and "Actual Behavior," and include specific examples to illustrate each case.

Identify the specific rule or constraint that was violated regarding null handling in the generated code for the use-case of [USE-CASE]. Please quote the exact clause from the relevant documentation that outlines how null values should be managed. Additionally, provide a brief explanation of the implications of this violation on the overall functionality and stability of the code.

In the function located at [FILE] on line [LINE], please add inline null checks for the variables that are currently causing crashes. Ensure that if any variable is found to be null or undefined, a default value is assigned or an appropriate error handling mechanism is implemented to manage the situation gracefully. Provide the updated code snippet with comments explaining the changes made for clarity.

Rewrite the function located at [FILE]:[LINE] to incorporate explicit null handling. Ensure that you check for null values using the format: 'if (variable == null) { handleError(); return; }'. Additionally, provide a brief explanation of how this change improves the function's stability and prevents potential crashes.

Modify the code at [FILE]:[LINE] to include a scoped null check. Ensure that this null check only applies to the variables that are directly causing the issue. Provide a brief explanation of how this change enhances safety and prevents potential null reference errors in the application.

Please review the functions in [FILE] and ensure they all handle null values according to the specified format: 'if (value == null) { return defaultValue; }'. For any functions that do not conform to this format, provide a detailed list of the necessary updates required to bring them into compliance. Additionally, explain the importance of consistent null handling in maintaining code quality and preventing runtime errors.

Examine the imports in [FILE] to identify any dependencies that do not properly handle null values. For each import, provide a detailed assessment of whether the associated functions can manage null inputs effectively. If any dependencies are found lacking, suggest specific modifications or alternative imports that would ensure robust null handling. Present your findings in a structured report format, including a summary of the issues and recommended fixes.

Run the application and conduct tests specifically targeting the scenarios where null values previously caused crashes. Please document each test case, including the input values used, the expected outcomes, and the actual results observed. Confirm that no errors occur during these tests and summarize your findings in a report format, highlighting any improvements in null handling.

Please provide a diff of the changes made to the function located at [FILE]:[LINE]. Ensure that you highlight the additions of null checks clearly, and also indicate any modifications made to the logic. Present the output in a structured format that distinguishes between added lines, removed lines, and unchanged lines for clarity.

Replay the original scenario that caused the runtime crash related to [USE-CASE] to verify that it no longer fails. Please provide a detailed account of the steps taken to reproduce the scenario, including the environment setup and any specific inputs used. Additionally, document any changes in behavior observed during the replay, noting any differences in output or performance compared to the previous version.

Please test the application for edge cases where null values might be introduced. Specifically, identify at least three scenarios where null values could occur and describe how the application behaves in each case. Confirm whether the application handles these scenarios gracefully without crashing, and provide a summary of your findings in a structured report format.

Please verify the output state of the function located at [FILE]:[LINE] after implementing null checks. Assess how the function behaves when it encounters null values, and provide a detailed explanation of the results. Include any discrepancies from the expected behavior and suggest further improvements if necessary.

Please provide a comprehensive guide on best practices for handling null or undefined values in code. Include specific strategies for checking variables before use, examples of common pitfalls that lead to runtime errors, and recommendations for implementing these checks effectively. Format the output as a structured document with sections for each best practice, including code snippets to illustrate each point.

Please create a conversation-starter template for ensuring null checks in new components. The template should include a clear guideline stating: 'For every new component, include null checks for all inputs.' Additionally, provide an example code snippet in the format: 'if (INPUT == null) { handleError(); return; }'. Ensure the template is structured for easy reference and understanding.

Draft a project specification message for the null handling use case titled "Project Spec for Null Handling." Clearly outline the requirement that all functions must include null checks for any external inputs. Additionally, explain the consequences of not adhering to this guideline, stating that failure to implement these checks will result in rejection during the code review process. Ensure the message is structured for clarity and includes a call to action for developers to review their code accordingly.

Please create a naming convention guideline for functions that handle external data. Specify that any function name must include 'CheckNull' to clearly indicate it performs null checks. Additionally, provide examples of function names that follow this convention and explain the importance of this practice in preventing null-related errors.

Please create a self-check guideline for developers to ensure proper null handling in their code. The guideline should include a checklist that confirms all variables are checked for null or undefined values before finalization. Additionally, provide specific examples of common scenarios where null checks are often missed, and suggest steps to flag any code that does not meet this requirement for review.