feat(frontend): add env-based api and contract config#53
Merged
joelpeace48-cell merged 4 commits intoFinesseStudioLab:mainfrom Apr 5, 2026
Merged
Conversation
|
@ACOB-DEV is attempting to deploy a commit to the joelpeace48-cell's projects Team on Vercel. A member of the Team first needs to authorize it. |
|
@ACOB-DEV Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
Please fix conflicts @ACOB-DEV |
# Conflicts: # frontend/README.md # frontend/src/Landing.jsx
ACOB-DEV
force-pushed
the
codex/issue-45-env-config
branch
from
e3e899a to
685d466
Compare
Contributor
Author
|
@joelpeace48-cell done. |
Contributor
Author
|
@joelpeace48-cell kindly review and merge |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
Centralize frontend API and Soroban configuration behind Vite env variables so deployments can change backend targets and optional rewards/campaign contract IDs without editing source files.
Closes #45 #32
Changes proposed
What were you told to do?
Read the API base URL and optional rewards/campaign contract IDs from VITE_* env values, use them for frontend fetch and Soroban wiring, and document the setup in the frontend README.
What did I do?
Shared frontend config
Frontend wiring and docs
Check List (Check all the applicable boxes)
Screenshots / Testing Evidence
Validated with npm run build --workspace=frontend. The frontend builds successfully with the shared config module and env-driven API/contract wiring in place.