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/override keytype sigtype #110

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Conversation

ieow
Copy link

@ieow ieow commented Feb 12, 2025

Motivation and Context

Jira Link:

Description

How has this been tested?

Screenshots (if appropriate):

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

  • My code follows the code style of this project. (run lint)
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.
  • All new and existing tests passed.
  • My code requires a db migration.

try {
if (this.updated && !MULTI_CLUSTER_NETWORKS.includes(this.network as TORUS_LEGACY_NETWORK_TYPE)) return this._nodeDetails;

const finalKeyType = keyType ?? this._keyType;
const finalSigType = sigType ?? this._sigType;
Copy link

@lwin-kyaw lwin-kyaw Feb 23, 2025

Choose a reason for hiding this comment

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

I think we should validate keyType and sigType before sending the request to fndServer to avoid unnecessary processing.

Even though the server performs the same validation, implementing client-side validation allows us to fail fast

Choose a reason for hiding this comment

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

I've addressed this and added the validation in the PR, #112

Choose a reason for hiding this comment

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

@ieow can I merge the PR, #112, into this?

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.

2 participants