-
-
Notifications
You must be signed in to change notification settings - Fork 980
feat: make scroll to top button attractive with hover effects #3605
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
Merged
Merged
Changes from 1 commit
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
ae17c97
Make Scroll to top button attractive with Hover effects
db4872a
Fix linting issues
c85eee5
Merge branch 'master' into scroll-btn
zalabhavy d462f7d
Merge branch 'master' into scroll-btn
zalabhavy 57b96c8
Merge branch 'master' into scroll-btn
zalabhavy d60aa1f
Merge branch 'master' into scroll-btn
zalabhavy 7938cc2
Merge branch 'master' into scroll-btn
zalabhavy 579803d
Merge branch 'master' into scroll-btn
zalabhavy a5e8835
Merge branch 'master' into scroll-btn
asyncapi-bot 29e9056
Merge branch 'master' into scroll-btn
anshgoyalevil File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🛠️ Refactor suggestion
Resolve Pipeline Failures by Fixing Tailwind Class Order and Multi-line Formatting
Currently, the pipeline fails due to formatting errors and a Tailwind CSS class ordering warning. You can move the
onClickprop to a new line and reorder classes to address both issues.Apply this diff to fix the pipeline failures:
📝 Committable suggestion
🧰 Tools
🪛 eslint
[error] 31-31: Replace
·className='rounded-full·bg-white·shadow-md·hover:bg-[#8851FB]·hover:scale-110·transition-all·duration-300·ease-in-out'·onClick={scrollUp}with⏎··········className='rounded-full·bg-white·shadow-md·hover:bg-[#8851FB]·hover:scale-110·transition-all·duration-300·ease-in-out'⏎··········onClick={scrollUp}⏎········(prettier/prettier)
🪛 GitHub Actions: PR testing - if Node project
[error] 31-31: Formatting error: Incorrect formatting of className and onClick props. Props should be on separate lines
[warning] 31-31: Invalid Tailwind CSS classnames order