NO-ISSUE Merged from release/0.2 #114

Merged
squid merged 3 commits from NO-ISSUE_merge_v0.2.2 into main 2025-08-04 07:35:46 +08:00
Owner

Description

Resolves conflicts.

Package Changes

No response

Screenshots

No response

Reference

NO_ISSUE

Checklist

  • A milestone is set
  • The related issuse has been linked to this branch
### Description Resolves conflicts. ### Package Changes _No response_ ### Screenshots _No response_ ### Reference _NO_ISSUE_ ### Checklist - [x] A milestone is set - [ ] The related issuse has been linked to this branch
squid added this to the 0.3 milestone 2025-08-04 07:34:24 +08:00
squid added 3 commits 2025-08-04 07:34:25 +08:00
BLOG-87 Fix to unify post content title color (#88)
All checks were successful
Frontend CI / build (push) Successful in 1m5s
64ebfaa3e9
### Description

- Enhance typography and color consistency in PostPreview and PostContentPage
- Add tailwind configuration for custom typography styles

### Package Changes

_No response_

### Screenshots

_No response_

### Reference

Resolves #87

### Checklist

- [x] A milestone is set
- [x] The related issuse has been linked to this branch

Reviewed-on: #88
Co-authored-by: SquidSpirit <squid@squidspirit.com>
Co-committed-by: SquidSpirit <squid@squidspirit.com>
NO-ISSUE build: update frontend version
All checks were successful
Frontend CI / build (push) Successful in 1m6s
Deployment / deployment (release) Successful in 7m9s
PR Title Check / pr-title-check (pull_request) Successful in 16s
8d7b59263d
Merge branch 'release/0.2' into NO-ISSUE_merge_v0.2.2
All checks were successful
Frontend CI / build (push) Successful in 1m8s
Auto Comment On PR / add_improve_comment (pull_request) Successful in 17s
PR Title Check / pr-title-check (pull_request) Successful in 16s
bc20385ff2
Collaborator

/improve

/improve
Collaborator

PR Code Suggestions

CategorySuggestion                                                                                                                                    Impact
Possible issue
Use theme colors for typography

The custom CSS variables like --color-gray-700 are used but appear undefined within
the Tailwind configuration or global CSS. To ensure the typography colors are
applied correctly and leverage Tailwind's theme, use theme() to reference colors
from the configured palette. This prevents broken styles if the custom variables are
not globally defined.

frontend/tailwind.config.js [8-12]

-'--tw-prose-body': 'var(--color-gray-700)',
-'--tw-prose-headings': 'var(--color-gray-800)',
-'--tw-prose-links': 'var(--color-gray-800)',
-'--tw-prose-bold': 'var(--color-gray-800)',
-'--tw-prose-quotes': 'var(--color-gray-800)'
+'--tw-prose-body': 'theme(colors.gray.700)',
+'--tw-prose-headings': 'theme(colors.gray.800)',
+'--tw-prose-links': 'theme(colors.gray.800)',
+'--tw-prose-bold': 'theme(colors.gray.800)',
+'--tw-prose-quotes': 'theme(colors.gray.800)'
Suggestion importance[1-10]: 8

__

Why: The suggestion correctly identifies that using theme() to reference colors directly from the Tailwind configuration is more robust than relying on custom CSS variables like --color-gray-700, which might not be defined or correctly resolved within the Tailwind context. This improves the correctness and maintainability of the styling.

Medium
## PR Code Suggestions ✨ <!-- --> <table><thead><tr><td><strong>Category</strong></td><td align=left><strong>Suggestion&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </strong></td><td align=center><strong>Impact</strong></td></tr><tbody><tr><td rowspan=1>Possible issue</td> <td> <details><summary>Use theme colors for typography</summary> ___ **The custom CSS variables like <code>--color-gray-700</code> are used but appear undefined within <br>the Tailwind configuration or global CSS. To ensure the typography colors are <br>applied correctly and leverage Tailwind's theme, use <code>theme()</code> to reference colors <br>from the configured palette. This prevents broken styles if the custom variables are <br>not globally defined.** [frontend/tailwind.config.js [8-12]](https://git.squidspirit.com/squid/blog/src/branch/NO-ISSUE_merge_v0.2.2/frontend/tailwind.config.js#L8-L12) ```diff -'--tw-prose-body': 'var(--color-gray-700)', -'--tw-prose-headings': 'var(--color-gray-800)', -'--tw-prose-links': 'var(--color-gray-800)', -'--tw-prose-bold': 'var(--color-gray-800)', -'--tw-prose-quotes': 'var(--color-gray-800)' +'--tw-prose-body': 'theme(colors.gray.700)', +'--tw-prose-headings': 'theme(colors.gray.800)', +'--tw-prose-links': 'theme(colors.gray.800)', +'--tw-prose-bold': 'theme(colors.gray.800)', +'--tw-prose-quotes': 'theme(colors.gray.800)' ``` <details><summary>Suggestion importance[1-10]: 8</summary> __ Why: The suggestion correctly identifies that using `theme()` to reference colors directly from the Tailwind configuration is more robust than relying on custom CSS variables like `--color-gray-700`, which might not be defined or correctly resolved within the Tailwind context. This improves the correctness and maintainability of the styling. </details></details></td><td align=center>Medium </td></tr></tr></tbody></table>
squid merged commit c66bc86771 into main 2025-08-04 07:35:46 +08:00
squid deleted branch NO-ISSUE_merge_v0.2.2 2025-08-04 07:35:46 +08:00
Sign in to join this conversation.
No description provided.