-
-
Notifications
You must be signed in to change notification settings - Fork 638
Add doctor checks for :async usage without React on Rails Pro #2010
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
Open
justin808
wants to merge
4
commits into
master
Choose a base branch
from
justin808/doctor-check-async-requires-pro
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+399
−0
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
a1aab6f
Add doctor checks to detect :async usage without React on Rails Pro
justin808 036aaa6
Improve doctor async checks: better error handling and comment filtering
justin808 4cdff17
Improve doctor async checks: enhance regex precision and add comprehe…
justin808 cda9a31
Refactor doctor async checks: extract constants and improve logging
justin808 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
Some comments aren't visible on the classic Files Changed page.
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.
Critical false positive bug: line 1238 doesn't verify :async presence.
The current logic produces false positives when a file has an uncommented
javascript_pack_tagwithout:asyncalongside a commented one with:async.Example scenario causing false positive:
Current behavior: Reports async usage (false positive)
Expected behavior: Should not report (only :async is commented)
Root cause: Line 1238 checks
line.include?("javascript_pack_tag")but doesn't verify the line contains:async, so any uncommented pack tag triggers detection even when it has no async option.Apply this fix:
This ensures only lines with both
javascript_pack_tagAND async indicators are considered, eliminating false positives.Note: This issue was previously flagged in past review comments but remains unfixed.