[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-03-31 UTC."],[[["Error messages should clearly identify the cause of the error, including specific invalid values or unmet requirements."],["Provide clear instructions on how to fix the problem, potentially using examples for better understanding."],["Write concise and understandable messages, using consistent terminology and appropriate language for the target audience."],["Maintain a positive and helpful tone without excessive apologies."]]],["Error messages should identify the cause, including invalid values and constraints. Explain the solution, using examples when helpful. Write clearly by being concise, avoiding double negatives, using consistent terminology, and targeting the appropriate audience. Format long messages well. Maintain a positive tone without being overly apologetic. These best practices are recommended for general error messages.\n"]]