Chore: UI bugs #624
Merged
Chore: UI bugs #624
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 ↗︎
|
kittybest
requested review from
ctrlc03,
crisgarner and
NicoSerranoP
as code owners
crisgarner
reviewed
Jan 31, 2025
kittybest
force-pushed
the
chore/ui-bugs
branch
from
88874c4 to
fdbfd2e
Compare
kittybest
force-pushed
the
chore/ui-bugs
branch
from
fdbfd2e to
80d8bce
Compare
This was referenced Feb 3, 2025
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.
Description
Found more ui small bugs that would affect usage.
ProjectItemrequire too many things instead of just a component, split the pure styling out asProjectItemContentProjectItemwidthisActivecondition judgement on nav bar tagsAllocateEquallyButtonandRemoveBallotButtonwhen it's not voting periodRelated issue(s)
close issue #622
Additional Notes
since this PR is forked from PR #620 , so only could be merged after 620 merged.
Confirmation
Important
We do not accept minor grammatical fixes (e.g., correcting typos, rewording sentences) unless they significantly improve clarity in technical documentation. These contributions, while appreciated, are not a priority for merging. If there is a grammatical error feel free to message the team.