Skip to content
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

refactor: use Signal::get_untracked() in non reactive contexts #800

Merged
merged 2 commits into from
Mar 10, 2025

Conversation

hrzlgnm
Copy link
Owner

@hrzlgnm hrzlgnm commented Mar 10, 2025

Also deduplicate the service_type input empty condition while deriving the signal.

Summary by Sourcery

Use Signal::get_untracked() in non-reactive contexts to avoid unnecessary re-renders.

Copy link

sourcery-ai bot commented Mar 10, 2025

Reviewer's Guide by Sourcery

This pull request replaces the usage of the reactive get() method with the non-reactive get_untracked() method on RwSignal in contexts where reactivity is not required. This change prevents unnecessary re-renders and side effects, improving performance. The changes were made in the Browse function and in the App function when initializing and updating the theme.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change Details Files
Replaced reactive get() calls with non-reactive get_untracked() calls in several places to prevent unnecessary re-renders or side effects in non-reactive contexts.
  • Replaced browsing.get() with browsing.get_untracked() in the Browse function.
  • Replaced service_type.get() with service_type.get_untracked() in the Browse function.
  • Replaced brand_colors.get() with brand_colors.get_untracked() when initializing the theme.
  • Replaced brand_colors.get() with brand_colors.get_untracked() when setting the dark theme.
  • Replaced brand_colors.get() with brand_colors.get_untracked() when setting the light theme.
src/app.rs

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!
  • Generate a plan of action for an issue: Comment @sourcery-ai plan on
    an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@github-actions github-actions bot added the bug Something isn't working label Mar 10, 2025
Copy link

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

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

Hey @hrzlgnm - I've reviewed your changes - here's some feedback:

Overall Comments:

  • It looks like you're consistently using get_untracked in these contexts, which is good for performance. Consider adding a comment explaining why get_untracked is necessary in these specific cases to improve readability.
Here's what I looked at during the review
  • 🟢 General issues: all looks good
  • 🟢 Security: all looks good
  • 🟢 Testing: all looks good
  • 🟢 Complexity: all looks good
  • 🟢 Documentation: all looks good

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@hrzlgnm hrzlgnm enabled auto-merge (squash) March 10, 2025 21:06
@hrzlgnm hrzlgnm removed the bug Something isn't working label Mar 10, 2025
@hrzlgnm hrzlgnm disabled auto-merge March 10, 2025 21:16
@hrzlgnm hrzlgnm enabled auto-merge (squash) March 10, 2025 21:17
@hrzlgnm hrzlgnm merged commit c7f23ba into main Mar 10, 2025
5 checks passed
@hrzlgnm hrzlgnm deleted the fix/untracked-warnings branch March 10, 2025 21:31
@hrzlgnm hrzlgnm changed the title fix: use Signal::get_untracked() in non reactive contexts refactor: use Signal::get_untracked() in non reactive contexts Mar 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant