Create redux logic for storing token settings - closes #1948 #1964
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 issue have I solved?
-- #1948
How have I implemented/fixed it?
Update the settings reducer file adding one more field token in the same way as the mobile team has it, then add a function that will help to validate and update the active token based on the incoming data.
In the other hand I update the actions/settings.js file for add the a new action creator that will be on charge to update the token of the settings reducer
How has this been tested?
Right now there is only logic for this functionality and not something that can be trigger from the UI so that way I tested was triggering/dispatching the settingsUpdateToken action with data and see if the reducer state update based on that.
You can change the active value from LSK to BTC and see how the active token now change.
Review checklist