Correctly override active preset - #5389
Merged
Merged
Conversation
nflaig
force-pushed
the
nflaig/correctly-update-preset
branch
from
April 19, 2023 20:21
4d04366 to
9d71502
Compare
nflaig
force-pushed
the
nflaig/correctly-update-preset
branch
from
April 19, 2023 20:24
9d71502 to
0aafe75
Compare
Contributor
Performance Report鉁旓笍 no performance regression detected Full benchmark results
|
nflaig
commented
Apr 20, 2023
wemeetagain
approved these changes
Apr 20, 2023
Member
|
馃帀 This PR is included in v1.8.0 馃帀 |
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
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.
Motivation
Fix for #4601 and #5387,
setActivePresetnow correctly overrides not only the variables that are exported individually/explicitly but also the exportedactivePresetobject.Description
BeaconPresetto type and renaming the file totypes.tsBeaconPresetactivePresetare overriddenNote: Initial implementation in #5387 did not filter out extraneous keys due to the fact that the destructuring did that already. However, since we override the
activePresetobject now I think it is better to apply filtering to not pollute the object as it is done in chainConfigToJson.