fix(billing): require org id for service/asset usage TASK-1476 #5443
Conversation
This file contains 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
rajpatel24
pushed a commit
that referenced
this pull request
Jan 28, 2025
### 📣 Summary Removes option for API calls to retrieve user-based service/asset usage. ### 💭 Notes We previously allowed for the possibility that users would not be organization members. If a user wasn't an org member, we used a separate API endpoint to retrieve their usage data. Now, however, from a frontend perspective users are always organization members and we should always use the organization usage endpoints. ### 👀 Preview steps 1. As a member of an MMO with at least one admin member, create and deploy a project and make a submission. 2. Access the organization usage page as an admin and view the per-project usage table. 3. On main, this table will be empty. On this PR branch, it will include the project. 4. Access the organization usage page as the owner and view the per-project usage table. 5. On main, the project will be shown as a draft. On this branch it will show up as deployed.
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.
🗒️ Checklist
<type>(<scope>)<!>: <title> TASK-1234frontendorbackendunless it's global📣 Summary
Removes option for API calls to retrieve user-based service/asset usage.
💭 Notes
We previously allowed for the possibility that users would not be organization members. If a user wasn't an org member, we used a separate API endpoint to retrieve their usage data. Now, however, from a frontend perspective users are always organization members and we should always use the organization usage endpoints.
👀 Preview steps