-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve review UI (a sequel to #545: Fix rating review overflow) #552
base: main
Are you sure you want to change the base?
Conversation
…th fixed widths, and fixed the remaining responsiveness issues
Should this be marked as a draft? |
I didn't know that was something you could do for pull requests, but yes, that would seem to apply. |
Just converted this to a draft, thanks for the heads up. However, I'd still like others (mainly @Awesome-E) to review this pr and let me kow their feedback. |
…rimary to reflect the Figma design, and made improvements to the sorting/filtering menu
Improved several aspects of PeterPortal reviews.
Description
This pull request is a continuation of pull request #545: Fix rating review overflow. As you’ll see, I made a lot more changes than just fixing the rating overflow, so I figured it’d be better to make a new branch. I do apologize in advance for the mess that I’ve caused, creating multiple pull requests and whatnot. Hopefully, it all works out in the end, with the best possible code being the output. In the future, I'll try to stick more closely with the corresponding pull request I'm fixing, and just create more issues whenever I find things that I think could be improved. I already have more ideas of how to improve reviews, but I didn't want to implement anything TOO drastic.
After pushing code to pull request #545 a few hours ago, I continued to work on the UI/UX for reviews, because while working I noticed many things that could be improved, and I was in the mood to fix them. I will admit, I got carried away with it, and many of the changes I made are not related to the original issue. However, I do believe that these changes are an improvement to the current UI/UX, and I hope you agree with me. Let me know your thoughts.
Note that this version that I’m committing is not ready to be merged. As you’ll see when you check it out, it has many red boxes, although they may be commented out. I use these to help me identify both the boundaries of elements, and what needs fixing. The latter will apply to you - anything that has a box around it still either needs to be fixed, or at least has a question corresponding to it. I’m mainly looking for feedback on my changes, which I can then implement, and THEN merge to main.
Things I fixed
Things that still need to be fixed
Screenshots
Before:
After:
Test Plan
Issues
Closes issue #304 and pull request #545