Skip to content

change linkClasses in FwbNavbarLink to be computed rather than only evaluated on mount to resolve #373 #375

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 2 commits into from
Apr 30, 2025

Conversation

thepurpleblob
Copy link

@thepurpleblob thepurpleblob commented Apr 25, 2025

The linkClasses const declared in FwbNavbarLink is just an ordinary constant. It should be reactive as it relies on the value of a prop.

Fix changes it to a computed value such that it will change when the prop changes. I assume that would be expected behaviour.

Fixes #373

Summary by CodeRabbit

Summary by CodeRabbit

  • Refactor
    • Improved reactivity of navigation link styling to better reflect active state changes.

Copy link
Contributor

coderabbitai bot commented Apr 25, 2025

Walkthrough

The change updates the linkClasses definition in the FwbNavbarLink.vue component from a static merged string to a Vue computed property. This adjustment ensures that the class list for the navigation link is now reactive and will automatically update when the isActive prop changes. No other logic or control flow in the component was modified.

Changes

File(s) Change Summary
src/components/FwbNavbar/FwbNavbarLink.vue Refactored linkClasses from a constant to a computed property to make class merging reactive.

Assessment against linked issues

Objective Addressed Explanation
Make linkClasses a computed property to ensure reactivity with props.isActive (#373)

Possibly related PRs

Poem

A hop, a skip, a reactive leap,
Now navbar links their classes keep
In sync with props that change and flow,
Watch them update—onward they go!
With computed flair, our code does shine,
🐇✨ Vue’s magic, simply divine!


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between cd21545 and 9de4614.

📒 Files selected for processing (1)
  • src/components/FwbNavbar/FwbNavbarLink.vue (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • src/components/FwbNavbar/FwbNavbarLink.vue

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
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

netlify bot commented Apr 25, 2025

Deploy Preview for sensational-seahorse-8635f8 ready!

Name Link
🔨 Latest commit 9de4614
🔍 Latest deploy log https://app.netlify.com/sites/sensational-seahorse-8635f8/deploys/681277fbbe71e700089046c5
😎 Deploy Preview https://deploy-preview-375--sensational-seahorse-8635f8.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

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: 0

🧹 Nitpick comments (1)
src/components/FwbNavbar/FwbNavbarLink.vue (1)

40-45: Good change making linkClasses reactive with computed!

Converting linkClasses from a static value to a computed property is a great fix for issue #373. This ensures the class list updates reactively when the isActive prop changes, rather than only being evaluated once on component mount.

However, there are some code style issues to fix:

 const linkClasses = computed(() => {
-    return twMerge(
-        defaultClasses,
-	props.isActive ? currentPageClasses: defaultStateClasses,
-    )
+  return twMerge(
+    defaultClasses,
+    props.isActive ? currentPageClasses : defaultStateClasses,
+  )
 })
🧰 Tools
🪛 ESLint

[error] 41-41: Expected indentation of 2 spaces but found 4.

(@stylistic/indent)


[error] 42-42: Expected indentation of 4 spaces but found 8.

(@stylistic/indent)


[error] 43-43: Unexpected tab character.

(@stylistic/no-tabs)


[error] 43-43: Expected indentation of 4 spaces but found 1 tab.

(@stylistic/indent)


[error] 43-43: Operator ':' must be spaced.

(@stylistic/space-infix-ops)


[error] 44-44: Expected indentation of 2 spaces but found 4.

(@stylistic/indent)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d718fd6 and cd21545.

📒 Files selected for processing (1)
  • src/components/FwbNavbar/FwbNavbarLink.vue (1 hunks)
🧰 Additional context used
🪛 ESLint
src/components/FwbNavbar/FwbNavbarLink.vue

[error] 41-41: Expected indentation of 2 spaces but found 4.

(@stylistic/indent)


[error] 42-42: Expected indentation of 4 spaces but found 8.

(@stylistic/indent)


[error] 43-43: Unexpected tab character.

(@stylistic/no-tabs)


[error] 43-43: Expected indentation of 4 spaces but found 1 tab.

(@stylistic/indent)


[error] 43-43: Operator ':' must be spaced.

(@stylistic/space-infix-ops)


[error] 44-44: Expected indentation of 2 spaces but found 4.

(@stylistic/indent)

@Sqrcz Sqrcz self-assigned this Apr 30, 2025
@Sqrcz Sqrcz added the 🪲 bug Something isn't working label Apr 30, 2025
Copy link
Collaborator

@Sqrcz Sqrcz left a comment

Choose a reason for hiding this comment

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

Good catch! Thank you 👏

+ return from arrow function simplified
@Sqrcz Sqrcz merged commit 7515aa3 into themesberg:main Apr 30, 2025
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🪲 bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

In FwbNavbarLink, twMerge should be in computed(), not just in the const declaration
2 participants