-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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: standardize export style to named exports #10630
Merged
kodiakhq
merged 13 commits into
discordjs:main
from
sdanialraza:refactor/standardize-export-style-to-named-exports
Jan 18, 2025
Merged
refactor: standardize export style to named exports #10630
kodiakhq
merged 13 commits into
discordjs:main
from
sdanialraza:refactor/standardize-export-style-to-named-exports
Jan 18, 2025
Conversation
This file contains 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
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 2 Skipped Deployments
|
sdanialraza
force-pushed
the
refactor/standardize-export-style-to-named-exports
branch
from
December 2, 2024 19:55
6b99372
to
d36072f
Compare
vladfrangu
requested changes
Dec 3, 2024
vladfrangu
previously approved these changes
Dec 5, 2024
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.
Good luck testing this XD
didinele
previously approved these changes
Dec 5, 2024
almeidx
force-pushed
the
refactor/standardize-export-style-to-named-exports
branch
from
December 5, 2024 20:56
a30e840
to
b5fd7f7
Compare
sdanialraza
force-pushed
the
refactor/standardize-export-style-to-named-exports
branch
from
December 8, 2024 23:06
9b09786
to
c0f24ea
Compare
sdanialraza
force-pushed
the
refactor/standardize-export-style-to-named-exports
branch
from
December 19, 2024 16:08
c0f24ea
to
0cc4d9e
Compare
sdanialraza
force-pushed
the
refactor/standardize-export-style-to-named-exports
branch
from
December 23, 2024 14:15
0cc4d9e
to
12b2c58
Compare
sdanialraza
force-pushed
the
refactor/standardize-export-style-to-named-exports
branch
3 times, most recently
from
January 15, 2025 01:42
ace2e82
to
5b8a84f
Compare
sdanialraza
force-pushed
the
refactor/standardize-export-style-to-named-exports
branch
from
January 16, 2025 16:06
2160e75
to
1b67050
Compare
Jiralite
approved these changes
Jan 18, 2025
vladfrangu
approved these changes
Jan 18, 2025
SpaceEEC
approved these changes
Jan 18, 2025
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.
🤞
almeidx
approved these changes
Jan 18, 2025
sdanialraza
deleted the
refactor/standardize-export-style-to-named-exports
branch
January 18, 2025 18:59
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Please describe the changes this PR makes and why it should be merged:
This standardizes the export style across the codebase by replacing default exports with named exports for consistency. It was pointed out internally here.
Status and versioning classification: