Coding patterns and best practices — React components, promise handling, and TypeScript conventions.
| Topic | Guide | Key Points |
|---|---|---|
| Promise handling | promise-handling.md | Always await or use void, never floating promises |
| React components | react-components.md | Named imports, functional components, no FC type |
| Restricted patterns | restricted-patterns.md | Forbidden: , direct hd-core import |
toLocaleLowerCase// ❌ FORBIDDEN - floating promise
apiCall();
// ✅ CORRECT
await apiCall();
// or
void apiCall(); // intentionally not awaited
// ❌ FORBIDDEN
import React, { FC } from 'react';
const MyComponent: FC<Props> = () => {};
// ✅ CORRECT
import { useState, useCallback } from 'react';
function MyComponent({ prop }: { prop: string }) {}
// ❌ FORBIDDEN
string.toLocaleLowerCase()
import { x } from '@onekeyfe/hd-core';
import { localDbInstance } from '...';
// ✅ CORRECT
string.toLowerCase()
const { x } = await CoreSDKLoader();
import { localDb } from '...';
/1k-date-formatting - Date and time formatting/1k-i18n - Internationalization and translations/1k-error-handling - Error handling patterns/1k-cross-platform - Platform-specific code/1k-code-quality - Linting and code quality/1k-performance - Performance optimization/1k-state-management - Jotai atom patterns/1k-architecture - Project structure and import rules/1k-code-quality - Lint fixes, pre-commit tasks