Feature implementation from commits 643773c..7e049ee

[codeOwlAI]

PR Summary

Enhance Hooks with Optional Parameters and Optimize Data Flow

Overview

This PR updates several hooks to support optional parameters, improves data flow optimization, and fixes potential null pointer exceptions. It also updates documentation URLs and implements a new useDebounce hook.

Change Types

Type	Description
Enhancement	Added optional parameters to hooks for better flexibility
Feature	Implemented new useDebounce hook for delayed value updates
Bugfix	Added null checks to prevent potential exceptions
Refactor	Optimized data flow in hooks with conditional processing
Docs	Updated LexDAO and Kleros terms URLs to new documentation site

---

Affected Modules

Module / File	Change Description
constants/src/config.ts	Updated documentation URLs for LexDAO and Kleros terms
hooks/src/useDebounce.ts	Implemented new React hook for value debouncing
hooks/src/useDetailsPin.ts	Added null check for 'details' parameter
hooks/src/useEscrowZap.ts	Refactored network configuration handling and milestone calculations
hooks/src/useFetchTokens.ts	Added optional 'enabled' parameter for conditional execution
hooks/src/useInvoiceCreate.ts	Added optional parameters and optimized details handling
hooks/src/useLock.ts	Added support for optional 'details' parameter
hooks/src/useResolve.ts	Added optional parameters and conditional error handling
utils/src/resolvers.ts	Updated Yup validation schema dependency format

---

Notes for Reviewers

• The hooks now support both direct 'details' objects and 'detailsHash' parameters
• Loading state logic has been made more complex to account for different data sources
• Error handling in useResolve now conditionally uses toast only when available

[codeowlai]

🐛 Correctness Issue

Chain-Specific Address Resolution Removed.

This change removes chainId-specific address lookup which will cause the contract to use incorrect addresses or fallback to '0x0'

Current Code (Diff):

-     address: networkConfig?.ZAP_ADDRESS ?? '0x0',
+     address: networkConfig[chainId]?.ZAP_ADDRESS ?? '0x0',

📝 Committable suggestion

‼️ IMPORTANT
Trust, but verify! 🕵️ Please review this suggestion with the care of a code archaeologist - check that it perfectly replaces the highlighted code, preserves all lines, maintains proper indentation, and won't break anything in production. Your future self will thank you! 🚀

Suggested change

	address: networkConfig?.ZAP_ADDRESS ?? '0x0',
	address: networkConfig[chainId]?.ZAP_ADDRESS ?? '0x0',

[codeowlai]

🐛 Correctness Issue

Complex Boolean Logic Creates Potential Loading State Bug.

The expression !(details || !detailsLoading) is unnecessarily complex and could lead to incorrect loading state determination which might cause UI inconsistencies.

Current Code (Diff):

-       !(details || !detailsLoading),
+       !details && detailsLoading,

📝 Committable suggestion

‼️ IMPORTANT
Trust, but verify! 🕵️ Please review this suggestion with the care of a code archaeologist - check that it perfectly replaces the highlighted code, preserves all lines, maintains proper indentation, and won't break anything in production. Your future self will thank you! 🚀

Suggested change

	!(details || !detailsLoading),
	!details && detailsLoading,

[codeowlai]

🐛 Correctness Issue

Missing error logging for null toast case.

When toast is null, errors are silently ignored without any logging, potentially hiding critical failures in production.

Current Code (Diff):

-       onError: error => {
-         if (toast) errorToastHandler('useResolve', error, toast);
+       onError: error => {
+         if (toast) errorToastHandler('useResolve', error, toast);
+         else logError('useResolve', error);
       },

📝 Committable suggestion

‼️ IMPORTANT
Trust, but verify! 🕵️ Please review this suggestion with the care of a code archaeologist - check that it perfectly replaces the highlighted code, preserves all lines, maintains proper indentation, and won't break anything in production. Your future self will thank you! 🚀

Suggested change

	onError: error => {
	if (toast) errorToastHandler('useResolve', error, toast);
	},
	onError: error => {
	if (toast) errorToastHandler('useResolve', error, toast);
	else logError('useResolve', error);
	},

[codeowlai]

🐛 Correctness Issue

Incorrect Loading State Logic.

The changed loading state logic using !(details || !detailsLoading) modifies the component's behavior and could cause UI inconsistencies.

Current Code (Diff):

-       !(details || !detailsLoading),
+       detailsLoading,

📝 Committable suggestion

‼️ IMPORTANT
Trust, but verify! 🕵️ Please review this suggestion with the care of a code archaeologist - check that it perfectly replaces the highlighted code, preserves all lines, maintains proper indentation, and won't break anything in production. Your future self will thank you! 🚀

Suggested change

	!(details || !detailsLoading),
	detailsLoading,