Skip to content

Conversation

@aurthitaacharya-afk
Copy link

@aurthitaacharya-afk aurthitaacharya-afk commented Jan 26, 2026

Fixes #965

What was the issue?

In the empty gallery state, the text “Go to Settings to add folders” was informational only and not clickable, which could confuse first-time users.

What I changed

  • Made the “Go to Settings” text clickable
  • Added visual cues (pointer cursor and underline)
  • Redirects users directly to the Settings page

Why this change

This improves user experience and discoverability by guiding users directly to the correct action when the gallery is empty.

Screenshots / Testing

  • Verified that clicking “Go to Settings” navigates to the Settings page successfully.

Summary by CodeRabbit

  • Documentation

    • Updated Discord community link formatting in documentation
  • Style

    • Enhanced text rendering in form elements with improved line spacing and padding to prevent text cutoff

✏️ Tip: You can customize this high-level summary in your review settings.

@github-actions github-actions bot added UI good first issue Good for newcomers labels Jan 26, 2026
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jan 26, 2026

📝 Walkthrough

Walkthrough

This pull request introduces minor updates: a label capitalization change in the README file and CSS styling additions to fix text rendering and padding issues for form controls and typographic elements, ensuring letters aren't cut off in the UI.

Changes

Cohort / File(s) Summary
Documentation
README.md
Updated Discord invitation link label from "Discord Server" to "DISCORD SERVER" (capitalization change).
Styling
docs/stylesheets/extra.css
Added CSS rules for form controls and typography (button, input, select, textarea, paragraph/list elements) within md-typeset, setting line-height: 1.5 and vertical padding (padding-top: 0.4rem, padding-bottom: 0.4rem) to prevent text cutoff and improve layout.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A hop and a skip, the text now sits tight,
With padding and height, it shines oh so bright!
Discord's name gleams in caps, proud and tall,
These polishes twinkle—small gifts after all! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 3
❌ Failed checks (3 warnings)
Check name Status Explanation Resolution
Title check ⚠️ Warning The PR title focuses on making 'Go to Settings' clickable in empty gallery state, which aligns with the main objective from issue #965. However, the actual changes include unrelated modifications to README.md and CSS styling. The title describes the primary objective (fixing empty gallery clickability) but the PR contains out-of-scope changes. Consider either splitting this into separate PRs or updating the title to reflect all changes included.
Linked Issues check ⚠️ Warning The PR claims to fix issue #965 (making 'Settings' text clickable in empty gallery), but the changeset only shows README.md and CSS modifications with no evidence of the actual empty gallery UI changes required. The PR appears to be missing the core implementation that makes the 'Settings' text clickable in the empty gallery state. Verify that the UI changes to the empty gallery component are included in this PR.
Out of Scope Changes check ⚠️ Warning The PR contains multiple changes unrelated to issue #965: updating README.md label capitalization and adding CSS text padding/line-height fixes. These are not part of the linked issue scope. Remove or separate the README.md and CSS styling changes into a different PR. Keep this PR focused solely on making the 'Settings' text clickable in the empty gallery state.
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🤖 Fix all issues with AI agents
In `@docs/stylesheets/extra.css`:
- Around line 315-327: The CSS block for selectors button, input, select,
textarea, .md-typeset p, and .md-typeset li contains syntax and cosmetic issues:
remove the stray backslash, correct the comment typo "bring" → "being", fix the
padding-bottom value from "0.4 rem" to "0.4rem", and normalize spacing around
colons (e.g., use "line-height: 1.5;" and "padding-top: 0.4rem; padding-bottom:
0.4rem;") so the rules parse correctly and consistently.

In `@README.md`:
- Line 9: The markdown link text contains extra spaces inside the square
brackets ("[ DISCORD SERVER ]"); edit the README link so the bracketed text has
no internal spaces (change "[ DISCORD SERVER ](https://discord.gg/hjUhu33uAn)"
to "[DISCORD SERVER](https://discord.gg/hjUhu33uAn)"), leaving the URL unchanged
to resolve the markdown lint warning and ensure consistent rendering.

Comment on lines +315 to 327
/* fix text padding issue -prevent letters from bring cut off */
button,
input,
select,
textarea,
.md-typeset p,
.md-typeset li {
line-height : 1.5;
padding-top: 0.4rem;
padding-bottom :0.4 rem;
}

\
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

Critical CSS syntax errors will break this rule.

Several issues in this block:

  1. Line 324: 0.4 rem has a space between the value and unit — CSS requires them to be joined (0.4rem). Browsers will ignore this invalid property.
  2. Line 322 & 324: Inconsistent spacing before colons (cosmetic but worth standardizing).
  3. Line 315: Typo "bring" → "being".
  4. Line 327: Stray backslash \ is invalid CSS and may cause parsing errors.
Proposed fix
-/* fix text padding issue -prevent letters from bring cut off */
+/* fix text padding issue - prevent letters from being cut off */
 button,
 input,
 select,
 textarea,
 .md-typeset p,
 .md-typeset li {
-  line-height : 1.5;
+  line-height: 1.5;
   padding-top: 0.4rem;
-  padding-bottom :0.4 rem;
+  padding-bottom: 0.4rem;
 }
-
-\
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
/* fix text padding issue -prevent letters from bring cut off */
button,
input,
select,
textarea,
.md-typeset p,
.md-typeset li {
line-height : 1.5;
padding-top: 0.4rem;
padding-bottom :0.4 rem;
}
\
/* fix text padding issue - prevent letters from being cut off */
button,
input,
select,
textarea,
.md-typeset p,
.md-typeset li {
line-height: 1.5;
padding-top: 0.4rem;
padding-bottom: 0.4rem;
}
🧰 Tools
🪛 Biome (2.1.2)

[error] 326-327: unexpected character \

(parse)

🤖 Prompt for AI Agents
In `@docs/stylesheets/extra.css` around lines 315 - 327, The CSS block for
selectors button, input, select, textarea, .md-typeset p, and .md-typeset li
contains syntax and cosmetic issues: remove the stray backslash, correct the
comment typo "bring" → "being", fix the padding-bottom value from "0.4 rem" to
"0.4rem", and normalize spacing around colons (e.g., use "line-height: 1.5;" and
"padding-top: 0.4rem; padding-bottom: 0.4rem;") so the rules parse correctly and
consistently.

&nbsp;&nbsp;&nbsp;<a href="https://discord.gg/hjUhu33uAn"><img src="https://github.com/user-attachments/assets/3ed93273-5055-4532-a524-87a337a4fbba" height="40"></a>

1. First, join the **[Discord Server](https://discord.gg/hjUhu33uAn) (Go to Projects->PictoPy)** to chat with everyone.
1. First, join the **[ DISCORD SERVER ](https://discord.gg/hjUhu33uAn) (Go to Projects->PictoPy)** to chat with everyone.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Remove spaces inside link brackets.

The markdown link has extra spaces inside the brackets ([ DISCORD SERVER ]), which triggers markdown lint warnings and may cause rendering inconsistencies across different markdown parsers.

Suggested fix
-1. First, join the **[ DISCORD SERVER ](https://discord.gg/hjUhu33uAn) (Go to Projects->PictoPy)** to chat with everyone.
+1. First, join the **[DISCORD SERVER](https://discord.gg/hjUhu33uAn) (Go to Projects->PictoPy)** to chat with everyone.
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
1. First, join the **[ DISCORD SERVER ](https://discord.gg/hjUhu33uAn) (Go to Projects->PictoPy)** to chat with everyone.
1. First, join the **[DISCORD SERVER](https://discord.gg/hjUhu33uAn) (Go to Projects->PictoPy)** to chat with everyone.
🧰 Tools
🪛 markdownlint-cli2 (0.18.1)

9-9: Spaces inside link text

(MD039, no-space-in-links)


9-9: Spaces inside link text

(MD039, no-space-in-links)

🤖 Prompt for AI Agents
In `@README.md` at line 9, The markdown link text contains extra spaces inside the
square brackets ("[ DISCORD SERVER ]"); edit the README link so the bracketed
text has no internal spaces (change "[ DISCORD SERVER
](https://discord.gg/hjUhu33uAn)" to "[DISCORD
SERVER](https://discord.gg/hjUhu33uAn)"), leaving the URL unchanged to resolve
the markdown lint warning and ensure consistent rendering.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

good first issue Good for newcomers UI

Projects

None yet

Development

Successfully merging this pull request may close these issues.

BUG: Empty gallery “Go to Settings” text is not clickable

1 participant