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

Node: add XLEN command #358

Merged
merged 3 commits into from
Jun 12, 2024
Merged

Conversation

aaron-congo
Copy link

No description provided.

*/
public xlen(
key: string,
): Promise<Record<string, Record<string, string[][]>>> {

Choose a reason for hiding this comment

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

Suggested change
): Promise<Record<string, Record<string, string[][]>>> {
): Promise<number> {

Choose a reason for hiding this comment

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

How it worked in tests?

Copy link
Author

@aaron-congo aaron-congo Jun 11, 2024

Choose a reason for hiding this comment

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

good catch, that was a copy-paste error. Good question! I'm not sure... I think we ran into a similar situation with Python at some point where the inner type was incorrect but the tests still pass. I think javascript and python had typing added after the language was initially created so it works a bit differently than Java, maybe the static analysis can't detect that the inner return value is the wrong type and the typing isn't checked during execution? Just a guess, idk

@aaron-congo aaron-congo merged commit 2debef0 into node/integ_acongo_xlen Jun 12, 2024
8 checks passed
@aaron-congo aaron-congo deleted the node/dev_acongo_xlen branch June 12, 2024 15:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants