refactor: standardize export style to named exports #10630
Draft
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
6b99372 to
d36072f
Compare
vladfrangu
requested changes
Dec 3, 2024
didinele
previously approved these changes
Dec 5, 2024
almeidx
force-pushed
the
refactor/standardize-export-style-to-named-exports
branch
from
a30e840 to
b5fd7f7
Compare
sdanialraza
force-pushed
the
refactor/standardize-export-style-to-named-exports
branch
from
9b09786 to
c0f24ea
Compare
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: