update ecosystem API routes to include team slug #6422
Merged
Conversation
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
|
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Member
Author
How to use the Graphite Merge QueueAdd either label to this PR to merge it via the merge queue:
You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. This stack of pull requests is managed by Graphite. Learn more about stacking. |
jnsdls
force-pushed
the
update_ecosystem_API_routes_to_include_team_slug
branch
from
8f0cb38 to
68dc2f8
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #6422 +/- ##
=======================================
Coverage 54.61% 54.61%
=======================================
Files 874 874
Lines 54723 54723
Branches 3710 3710
=======================================
Hits 29886 29886
Misses 24742 24742
Partials 95 95
🚀 New features to boost your workflow:
|
Contributor
size-limit report 📦
|
MananTank
approved these changes
Mar 5, 2025
Contributor
Merge activity
|
Updates ecosystem API endpoints to be scoped under team routes
The ecosystem wallet API endpoints have been updated to be scoped under team routes, ensuring proper data isolation between teams. All ecosystem-related API calls now include the team ID or slug in the path.
Key changes:
- Updated API endpoints from `/v1/ecosystem-wallet/*` to `/v1/teams/{teamIdOrSlug}/ecosystem-wallet/*`
- Added team slug parameter to ecosystem fetch and list operations
- Modified React hooks to include team context in query keys
- Updated component props to pass team information through the component tree
This change ensures ecosystem wallets are properly scoped to their respective teams and maintains data isolation between different team contexts.
<!-- start pr-codex -->
---
## PR-Codex overview
This PR updates various functions and components within the ecosystem module to include `team_slug` as a parameter. This change enhances the ability to fetch ecosystems and their details specific to a team, improving data handling across the application.
### Detailed summary
- Updated `fetchEcosystem` to accept `team_slug`.
- Modified `fetchEcosystemList` to include `team_slug`.
- Adjusted the `useEcosystemList` hook to utilize `teamIdOrSlug`.
- Enhanced `useEcosystem` to accept `teamIdOrSlug`.
- Updated components to pass `team_slug` where necessary.
- Changed redirect logic to incorporate team-specific ecosystems.
> ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}`
<!-- end pr-codex -->
graphite-app
bot
force-pushed
the
update_ecosystem_API_routes_to_include_team_slug
branch
from
68dc2f8 to
d753201
Compare
graphite-app
bot
deleted the
update_ecosystem_API_routes_to_include_team_slug
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Updates ecosystem API endpoints to be scoped under team routes
The ecosystem wallet API endpoints have been updated to be scoped under team routes, ensuring proper data isolation between teams. All ecosystem-related API calls now include the team ID or slug in the path.
Key changes:
/v1/ecosystem-wallet/*to/v1/teams/{teamIdOrSlug}/ecosystem-wallet/*This change ensures ecosystem wallets are properly scoped to their respective teams and maintains data isolation between different team contexts.
PR-Codex overview
This PR focuses on enhancing the ecosystem-related functions by adding
team_slugas a parameter in various API calls and hooks, ensuring that ecosystem data is fetched in the context of a specific team.Detailed summary
fetchEcosystemandfetchEcosystemListto includeteam_slug.useEcosystemanduseEcosystemListto acceptteamIdOrSlug.team_slugin the URL.team_slugwhere necessary.