add screenshots to the readme#70
Conversation
📝 WalkthroughWalkthroughThis pull request adds visual documentation to the README with four app screenshots (Wallet, Swap Page, Ongoing Swap, and Swap Report) and expands the CSS utility library with new layout, spacing, color, and styling utilities including border colors, background colors, and custom property declarations. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@src/styles/output.css`:
- Around line 551-554: Stylelint is flagging declaration-empty-line-before
inside the generated translate utility blocks (e.g., the .-translate-x-1 rule);
fix by inserting a blank line between each declaration in those utility CSS
rules (for example between the --tw-translate-x declaration and the translate
declaration) so each property is separated by a single empty line, or
alternatively update the lint config to ignore generated files if these are
produced output files; locate the translate utility selectors (like
.-translate-x-1 and the other translate variants referenced around the same
area) and apply the blank-line separation consistently across them.
ℹ️ Review info
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
⛔ Files ignored due to path filters (4)
screenshot/report1.pngis excluded by!**/*.pngscreenshot/swap.pngis excluded by!**/*.pngscreenshot/swap1.pngis excluded by!**/*.pngscreenshot/wallet.pngis excluded by!**/*.png
📒 Files selected for processing (2)
README.mdsrc/styles/output.css
| .-translate-x-1 { | ||
| --tw-translate-x: calc(var(--spacing) * -1); | ||
| translate: var(--tw-translate-x) var(--tw-translate-y); | ||
| } |
There was a problem hiding this comment.
Resolve Stylelint empty-line errors in translate utilities.
Stylelint reports declaration-empty-line-before at Line 553, Line 557, and Line 561. Add blank lines between declarations (or adjust the lint rule for generated CSS) to unblock linting.
🧹 Suggested formatting fix
.-translate-x-1 {
--tw-translate-x: calc(var(--spacing) * -1);
+
translate: var(--tw-translate-x) var(--tw-translate-y);
}
@@
.-translate-y-1 {
--tw-translate-y: calc(var(--spacing) * -1);
+
translate: var(--tw-translate-x) var(--tw-translate-y);
}Also applies to: 559-562
🧰 Tools
🪛 Stylelint (17.3.0)
[error] 553-553: Expected empty line before declaration (declaration-empty-line-before)
(declaration-empty-line-before)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@src/styles/output.css` around lines 551 - 554, Stylelint is flagging
declaration-empty-line-before inside the generated translate utility blocks
(e.g., the .-translate-x-1 rule); fix by inserting a blank line between each
declaration in those utility CSS rules (for example between the --tw-translate-x
declaration and the translate declaration) so each property is separated by a
single empty line, or alternatively update the lint config to ignore generated
files if these are produced output files; locate the translate utility selectors
(like .-translate-x-1 and the other translate variants referenced around the
same area) and apply the blank-line separation consistently across them.
fixes #68 : adds screenshots in readme
Summary by CodeRabbit
Documentation
Style