1K Error Handling

What it does

The 1K Error Handling skill provides guidance and best practices for implementing robust error handling within a OneKey codebase. It focuses on ensuring errors are properly managed, logged, and presented to users in a user-friendly way. The skill emphasizes using try/catch blocks, providing fallbacks, and utilizing the useAsyncCall hook to manage loading and error states effectively.

When to use it

• When developing asynchronous operations that may fail (e.g., API calls).
• When designing user interfaces where errors need to be gracefully handled and displayed.
• During code reviews to ensure adherence to established error handling patterns.
• To prevent "silent" error swallowing, which can lead to difficult-to-debug issues.
• When integrating with APIs or services that might return unexpected errors.

Key capabilities

• Try/Catch Blocks: Guidance on using try...catch blocks for asynchronous operations.
• Fallback Values: Implementing fallback mechanisms when an operation fails.
• useAsyncCall Hook: Utilizing the useAsyncCall hook to manage loading, error, and result states within components.
• User-Friendly Error Messages: Providing clear and helpful error messages to users.
• Error Logging: Ensuring errors are logged for debugging purposes.

Example prompts

• "Show me an example of using a try/catch block in OneKey."
• "How do I use the useAsyncCall hook to handle errors?"
• "What's the best way to display an error message to the user after a form submission fails?"

Tips & gotchas

• This skill is specifically tailored for the OneKey codebase and relies on its conventions, particularly the useAsyncCall hook.
• Avoid "silent" error swallowing; always log errors even if you don't handle them immediately.
• Refer to the detailed guide in error-handling.md for more comprehensive patterns and examples.