This repository has been archived by the owner on Jun 6, 2023. It is now read-only.
UI Rewrite #80
Draft
UI Rewrite #80
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
kiriDevs
added
enhancement
👇 Click on the image for a new way to code review
Legend |
Deploying with
|
| Latest commit: |
a4eec11
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://9500e81d.vplan.pages.dev |
| Branch Preview URL: | https://ui-rewrite.vplan.pages.dev |
It was duplicate code before
The ESLint pre-commit hook didn't prevent the commit with the warning, should fix that.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 will implement a complete overhaul of the user interface. The recent change on the mobile UI (#66), which actually just changed the actual plan viewer, will be incorporated in a new frame together with the existing table view for Desktops [subject to change]. This new frame will allow the user to pick the date that they want to see the plan for from a list of multiple possibilities, also allowing for accessing past plans or substitution plans in the far future, if available.
react-router-domwill be used for implementing client-side URL routing, making navigation-related state management easier, while also making it possible for users to share or save direct links to specific plans or sections of the site.Issue Mentions
The following issues are either implemented in this PR or are made irrelevant by this PR, or will be at the point that this PR leaves the "draft" status.
Dateinput field #29