-
Notifications
You must be signed in to change notification settings - Fork 374
fix(function): support multiline import type statements in import scanning #4872
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
lightstrike
wants to merge
2
commits into
supabase:develop
Choose a base branch
from
lightstrikelabs:lightstrikelabs/fix/multi-line-function-type-imports
base: develop
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.
+50
−1
Open
Changes from all commits
Commits
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,22 @@ | ||
| // Test file for multiline import type statements | ||
| // This pattern was broken before the [\s\S]*? fix | ||
|
|
||
| // Multiline import type - should be matched by the regex | ||
| import type { | ||
| Database, | ||
| Json | ||
| } from '../types/database.ts' | ||
|
|
||
| // Single line import type - should also work | ||
| import type { Database as DB } from '../types/database.ts' | ||
|
|
||
| // Re-export type to verify export pattern | ||
| export type { Database } from '../types/database.ts' | ||
|
|
||
| // Multiline export type | ||
| export type { | ||
| Json | ||
| } from '../types/database.ts' | ||
|
|
||
| // Non-braced default type import - exercises the [\s\S]*? branch on single-line | ||
| import type Database from '../types/database.ts' |
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,11 @@ | ||
| export type Database = { | ||
| public: { | ||
| Tables: { | ||
| users: { | ||
| Row: { id: string; name: string } | ||
| } | ||
| } | ||
| } | ||
| } | ||
|
|
||
| export type Json = string | number | boolean | null | { [key: string]: Json } | Json[] |
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.
Hey, thanks for tracking this down! The
[\s\S]*?change works, but I'm a little hesitant to widen the catch-all branch to match across newlines for everything — even with the lazy quantifier it feels like a broader change than what we need here.The root issue is that
import type { ... }doesn't hit the braced branch becausetypesits between the whitespace and{. What if we handled that more explicitly instead?Adding
(?:type\s+)?letsimport type { Foo, Bar }fall into the{[^{}]+}branch, which already crosses line boundaries fine. That way.*?stays single-line and we're only changing the behavior for actualtypeimports rather than everything.Happy to be wrong if there's a case I'm missing though do you have a test that the
(?:type\s+)?approach wouldn't cover?