Description:
Blockchain transactions inherently suffer from latency ranging from a few seconds to a minute while blocks clear. An exceptional user experience masks this latency with proactive notifications. This issue focuses entirely on designing and implementing a global, robust Toast Notification system utilizing shadcn/ui. When a user signs an escrow deposit or a generic job creation mechanism, the UI must immediately spawn a "Processing..." toast. When the backend or direct blockchain node confirms the transaction landed successfully, the toast dynamically updates into a success state featuring the transaction hash link. Similarly, error states like "Wallet Connection Dropped" or "Insufficient Escrow Funds" require deeply descriptive toasts to prevent severe user configuration frustration.
Requirements:
- Implement global provider wrappers enabling asynchronous toast spawning from any deeply nested component context.
- Design three highly explicit states: Information (Gray/Blue), Warning/Processing (Yellow/Animated Spinner), Critical Success/Error (Green/Red).
- Intercept and format complicated underlying Stellar SDK or Axum backend error codes into human-readable snippets.
- Include auto-timeout functionalities ensuring the interface is not cluttered with dead alert fragments.
Acceptance Criteria:
- Firing off a contract modification instantaneously provokes an informative visual tracking toast unconditionally.
- Complex backend error dumps are gracefully masked behind succinct UI explanations (e.g., "Not Authorized").
- The global notification mechanic functions cleanly without triggering extraneous component re-renders.
E2E Testing and CI/CD Integrations
Description:
Blockchain transactions inherently suffer from latency ranging from a few seconds to a minute while blocks clear. An exceptional user experience masks this latency with proactive notifications. This issue focuses entirely on designing and implementing a global, robust Toast Notification system utilizing
shadcn/ui. When a user signs an escrow deposit or a generic job creation mechanism, the UI must immediately spawn a "Processing..." toast. When the backend or direct blockchain node confirms the transaction landed successfully, the toast dynamically updates into a success state featuring the transaction hash link. Similarly, error states like "Wallet Connection Dropped" or "Insufficient Escrow Funds" require deeply descriptive toasts to prevent severe user configuration frustration.Requirements:
Acceptance Criteria:
E2E Testing and CI/CD Integrations