refactor: dashboard chains usage and HUMAN App errors - #3722
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. 5 Skipped Deployments
|
vercel
Bot
temporarily deployed
to
Preview – human-dashboard-frontend
December 18, 2025 11:14
Inactive
vercel
Bot
temporarily deployed
to
Preview – human-dashboard-frontend
December 18, 2025 11:32
Inactive
vercel
Bot
temporarily deployed
to
Preview – human-dashboard-frontend
December 18, 2025 12:41
Inactive
vercel
Bot
temporarily deployed
to
Preview – human-dashboard-frontend
December 18, 2025 12:49
Inactive
flopez7
approved these changes
Dec 18, 2025
flopez7
suggested changes
Dec 18, 2025
vercel
Bot
temporarily deployed
to
Preview – human-dashboard-frontend
December 18, 2025 15:04
Inactive
flopez7
approved these changes
Dec 18, 2025
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.
Issue tracking
Freestyle
Context behind the change
ERR_INVALID_URL, that happens in case if somebody tries to use chain id that is not configured (e.g. 1338 - localhost). Addressed that by refactoring the way of working with chain ids, so only expected values allowed, not every chain supported by SDKHow has this been tested?
Release plan
WEB3_ENVvar for dashboard serverPotential risks; What to monitor; Rollback plan
Should be none