Open
Conversation
* Also include creation of container-stack to make standard the spacing between elements inside containers.
7 tasks
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
7 tasks
7 tasks
* Also update our custom mantine.d.ts to to make TS aware of the change.
brunomenezes
force-pushed
the
feat/application-summary-page
branch
from
007b70a to
8bd8a9e
Compare
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
1 participant
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.
Summary
Code changes to add an "application home" instead of navigating straight to the list of epochs. The page contains a summary of the current status of application. tldr: Summary of status and quick access to epochs and active tournament if there is one.
Also, refactor a few components and improve syncing of colour-scheme changes between the Storybook toolbar and the switch in the application header. The commits are separated so it is easy to follow the changes if needed.
It closes the issue: #425
A test can be performed using the latest Cartesi CLI, ensuring the mock is disabled (default). Or a running rollups-node with an application, but update the environment variables accordingly.
But here is a storybook chromatic link: Application Summary Story
PS: In the in the chromatic story page just don't click the anchors because it is a Story and leads nowhere.