fix(v2.8): wasm config to use default config #220
Merged
+33
−129
Conversation
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
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## release/v2.8 #220 +/- ##
=============================================
Coverage 68.13% 68.13%
=============================================
Files 45 45
Lines 2150 2150
=============================================
Hits 1465 1465
Misses 524 524
Partials 161 161
|
javiersuweijie
approved these changes
Nov 27, 2023
tuky191
approved these changes
Nov 28, 2023
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.
WasmD 0.4x introduced breaking changes with the configuration of the environment by changing the name of the variables. To avoid possible issues in the future we remove the wasm configuration from core and use directly the one from wasmd package.