api-core to use named export instead of * #124
Closed
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
|
Deploy preview for jellyfish-defi canceled. Built with commit e0659e0 https://app.netlify.com/sites/jellyfish-defi/deploys/607720c6f13020000803f810 |
defichain-bot
added
area/jellyfish-api-core
kind/refactor
size-limit report 📦
|
|
Closes in favour of #130 |
eli-lim
pushed a commit
that referenced
this pull request
Mar 27, 2022
canonbrother
pushed a commit
that referenced
this pull request
Jun 1, 2022
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.
What kind of PR is this?:
/kind refactor
What this PR does / why we need it:
To prevent conflicts due to the massive amount of data to type, export should be named.
/cc @canonbrother might cause your pending PR to break, hence this should merge after #112 and then this PR should be updated.