-
Notifications
You must be signed in to change notification settings - Fork 245
ts-migration/index #372
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
ts-migration/index #372
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
182f9af
chore(index): convert to typescript
G-Rath 02ec3fa
chore(index): use `module.exports`
G-Rath 59ec9d7
chore: use reduce
SimenB e244b55
chore(index): use `parse` instead of `basename`
G-Rath 0b922f3
chore(index): `parse` rule files before `filter`ing
G-Rath 4955d0b
chore: remove files not rules
SimenB 8021495
chore: "fix" type error
SimenB 1f3c447
chore: purify reduce
SimenB 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
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.
Uh oh!
There was an error while loading. Please reload this page.
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.
This is actually surprisingly "slow" vs using an assignment, b/c everytime you're creating a new object & copying all the keys.
It's by far not a big deal, and even less so since we're doing it the once (I hope? I assume the way eslint runs it typically reuses the same node process), but it's an interesting little fact.
(That might have changed in later versions of node - iirc I last tested this on node8)
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.
doing it once during
require, yeah - probably not even measurable except in micro benchmarks. Nothing compared to the FS operations in the same file 🙂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.
and yeah, object spread has gotten way quicker (although it's currently transpiled down by babel until we drop node 6)
https://twitter.com/bmeurer/status/1015105293301280768?lang=en