Refactor Hooks into appData and userData Folders #106
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🚀 Summary
This PR reorganizes the project’s hooks by separating them into
appData
anduserData
folders.appData
now holds hooks and models related to application-level data (e.g., market, ads, fiat/countries, etc.).userData
now holds hooks and models tied to user-specific information (e.g., profile, wallet, reviews, KYC, pay methods, etc.).This improves project structure, maintainability, and discoverability of hooks by grouping them logically.
🧩 Related Issues / Tasks
N/A
🛠️ Type of Change
✅ Checklist
npm run format
ornpx prettier --write .
)📸 Screenshots / Videos (UI changes only)
N/A
🧪 Test Plan
appData
anduserData
function as expected.