Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Support Multiple Derivation Paths in UI #317

Merged
merged 3 commits into from
Jun 7, 2022

Conversation

kujtimprenkuSQA
Copy link
Contributor

@kujtimprenkuSQA kujtimprenkuSQA commented Jun 3, 2022

Description

  • Added Support Multiple Derivation Paths in UI.

Closes # (issue)

Checklist:

  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings

Type of change. This type of change is the main reason for the PR.

  • FIX - a PR of this type patches a bug.
  • FEATURE - a PR of this type introduces a new feature.
  • BUILD - a PR of this type introduces build changes.
  • CI - a PR of this type introduces CI changes.
  • DOCS - a PR of this type introduces DOCS improvement.
  • STYLE - a PR of this type introduces style changes.
  • REFACTOR - a PR of this type introduces refactoring.
  • PERFORMANCE - a PR of this type introduces performance changes.
  • TEST - a PR of this type adds more tests.
  • CHORE - a PR introduces other changes than the specified above.

Breaking changes

  • BREAKING CHANGE - SPECIFY: _______
  • NO BREAKING CHANGE - this PR doesn't contain any breaking changes and it's backwards compatible

@kujtimprenkuSQA kujtimprenkuSQA marked this pull request as ready for review June 3, 2022 15:04
@github-actions github-actions bot changed the title Support Multiple Derivation Paths in UI feat: Support Multiple Derivation Paths in UI Jun 3, 2022
amirsaran3
amirsaran3 previously approved these changes Jun 6, 2022
Comment on lines 35 to 47
const handleDerivationPathRemove = (index: number) => {
const newPaths = [...derivationPaths];
newPaths.splice(index, 1);
setDerivationPaths(newPaths);
};

const handleDerivationPathChange = (
index: number,
e: ChangeEvent<HTMLInputElement>
) => {
const newPaths = [...derivationPaths];
newPaths[index].path = e.target.value;
setDerivationPaths(newPaths);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When deriving state from previous state like this, we should use the function parameter for setState

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the review, I had some free time and adjusted the code.

@lewis-sqa lewis-sqa merged commit 908ab20 into dev Jun 7, 2022
@lewis-sqa lewis-sqa deleted the SQAC-163/ui-support-multiple-derivation-paths branch June 7, 2022 07:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants