Skip to content

Commit 9ebe8d3

Browse files
committed
Infinite plugin yay!
1 parent 6a82ac2 commit 9ebe8d3

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

51 files changed

+5548
-421
lines changed

AGENTS.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -108,3 +108,13 @@ The following documentation files provide detailed guidance for specific areas o
108108

109109
**When to read**: Before migrating ramp plugins from legacy provider architecture to new ramp plugin architecture or when creating new ramp plugins
110110
**Summary**: Comprehensive migration guide for removing FiatPluginUi abstraction and using direct API imports. Covers migration of toasts, modals, navigation, permissions (with important boolean logic inversion note), wallet operations, and environment configuration requirements. Includes detailed steps for creating init options cleaners, validating plugin initialization, and registering plugins in envConfig. Also explains how to migrate getSupportedAssets initialization logic to an internal fetchProviderConfig function with 2-minute TTL caching. Essential for converting legacy fiat providers to new ramp plugins and ensuring proper type safety.
111+
112+
### `docs/infinite-headless-api.md`
113+
114+
**When to read**: When integrating with Infinite's Headless SDK for wallet authentication, KYC, quotes, or transfers
115+
**Summary**: Complete API documentation for Infinite's Headless SDK. Covers wallet-based authentication flow using EIP-191 message signing, simplified customer onboarding with automatic wallet association, bank account management, real-time quotes for on-ramp/off-ramp conversions, and transfer execution with ACH payments. Includes detailed error codes, security best practices, and Edge Wallet-specific configuration (org_edge_wallet_main). Note that API Key is no longer required - only Organization ID and JWT tokens for authenticated endpoints.
116+
117+
### `docs/module-file-guidelines.md`
118+
119+
**When to read**: Before creating or modifying any TypeScript/JavaScript files or modules
120+
**Summary**: Comprehensive guidelines for organizing code files with strict ordering rules: types → constants → functions, with exports always preceding non-exports within each category. Explains the three-category structure where exported types come before non-exported types, exported constants before non-exported constants, and exported functions before non-exported functions. Provides detailed examples for different module types (React components, utilities, workflows), common violations to avoid, and visual separation techniques. Essential reading for maintaining consistent, scannable, and maintainable code structure across the codebase.

0 commit comments

Comments
 (0)