Skip to content

Frontend state management and providers #572

Closed

Description

@codebestia

Write apps/web/docs/concepts-state-management.md covering AuthProvider/AuthContext/useAuth, WalletContext, ProtectedRoute and app/providers.tsx: the provider tree, what state lives where, and why there is no global store library.

Acceptance criteria:

  • The provider nesting order is documented with the reason for it
  • Each context's state, actions and consumers are documented
  • Documents ProtectedRoute's redirect behaviour and the loading state that must be handled before it can decide
  • Explains the boundary between context state, server state fetched per route, and IndexedDB-persisted state

Activity

  1. Essence-3 commented on Aug 27, 2026

    @Essence-3

    @Essence-3 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

    Hi, I have a solution to this issue and I would love to work on it.

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @Essence-3 to this issue.

  2. promisszn commented on Aug 30, 2026

    @promisszn
    Contributor

    @promisszn has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

    Hi, I'd like to work on this issue. I'll write apps/web/docs/concepts-state-management.md documenting AuthProvider/AuthContext/useAuth, WalletContext, ProtectedRoute, and app/providers.tsx, covering the provider nesting order and its rationale, each context's state/actions/consumers, ProtectedRoute's redirect and loading behavior, and the boundary between context state, per-route server state, and IndexedDB-persisted state. I'll verify the doc matches the actual provider tree before opening a PR.

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @promisszn to this issue.

  3. drips-wave commented on Aug 30, 2026

    @drips-wave

    Congratulations, @promisszn! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

    🧑‍💻 @promisszn: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

    Warning

    When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

    🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

    🌊 Happy Wave 🌊

  4. added a commit that references this issue on Aug 30, 2026
    ca440c8
  5. github-actions commented on Aug 30, 2026

    @github-actions

    Closed by #595, merged into dev.

  6. drips-wave commented on Aug 30, 2026

    @drips-wave

    This issue has been completed by @promisszn as part of the Stellar Wave Program's 8th Wave 🥳

    😎 @promisszn: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

    🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Stellar WaveIssues in the Stellar wave programdocumentationImprovements or additions to documentationfrontend

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions