feat: hook up project resources API to resources widget #8657
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Skipped Deployment
|
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.OpenSSF Scorecard
Scanned Files |
sjaanus
approved these changes
Nov 5, 2024
thomasheartman
deleted the
feat/1-3063-add-connected-envs-data-project-resources
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.
This PR wires up the connectedenvironments data from the API to the resources widget.
Additionally, it adjusts the orval schema to add the new connectedEnvironments property, and adds a loading state indicator for the resource values based on the project status endpoint response.
As was discussed in a previous PR, I think this is a good time to update the API to include all the information required for this view. This would get rid of three hooks, lots of loading state indicators (because we can do them individually; check out 0a334f9) and generally simplify this component a bit.
Here's the loading state:
