-
Notifications
You must be signed in to change notification settings - Fork 0
update transpile.js #11
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 all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
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,19 @@ | ||
| const fs = require('fs'); | ||
| const { execSync } = require('child_process'); | ||
|
|
||
| describe('transpileCommand CLI', () => { | ||
| beforeAll(() => { | ||
| // Create a test config file before running the tests | ||
| fs.writeFileSync('test-config.json', JSON.stringify({ option: true })); | ||
| }); | ||
|
|
||
| afterAll(() => { | ||
| // Clean up the test config file after tests are done | ||
| fs.unlinkSync('test-config.json'); | ||
| }); | ||
|
|
||
| test('CLI runs with a specified config file', () => { | ||
| const output = execSync('node src/cli.js transpile --config test-config.json').toString(); | ||
| expect(output).toBeDefined(); | ||
| }); | ||
| }); |
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.
Overly Complex Exclude Patterns Assignment
Tell me more
What is the issue?
Complex one-liner with multiple logical operators and array handling makes the code hard to read and understand at a glance.
Why this matters
The nested ternary and multiple OR operators create cognitive load when trying to understand the fallback logic for exclude patterns.
Suggested change ∙ Feature Preview
Provide feedback to improve future suggestions
💬 Looking for more details? Reply to this comment to chat with Korbit.