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

Enabled 3rd party imports #46

Merged
merged 4 commits into from
Nov 28, 2023
Merged

Enabled 3rd party imports #46

merged 4 commits into from
Nov 28, 2023

Conversation

KuphJr
Copy link
Contributor

@KuphJr KuphJr commented Nov 27, 2023

No description provided.

bolekk
bolekk previously approved these changes Nov 28, 2023
Copy link
Contributor

@bolekk bolekk left a comment

Choose a reason for hiding this comment

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

LGTM

README.md Outdated
@@ -6,6 +6,7 @@ Up-to-date documentation on Chainlink Functions can be found [here](https://docs

# Table of Contents

- [functions-toolkit](#functions-toolkit)
Copy link
Collaborator

@zeuslawyer zeuslawyer Nov 28, 2023

Choose a reason for hiding this comment

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

nit: not sure we need this in the TOC given the best it will do is move readers 9 lines up?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Fixed this. Thanks!

'const { format } = await import("npm:date-fns"); return Functions.encodeString(format(new Date(), "yyyy-MM-dd"));',
})

expect(Buffer.from(result.responseBytesHexstring?.slice(2) as string, 'hex').length).toEqual(
Copy link
Collaborator

Choose a reason for hiding this comment

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

should we be testing that the import works as expected by asserting against the value of the result hex versus the length of the hex?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

If the import doesn't work, then this whole this will just throw an error, so I don't think this is needed.

Copy link
Collaborator

Choose a reason for hiding this comment

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

@KuphJr sorry wasnt clear- - was suggesting an alternate assert on this existing test

Copy link
Collaborator

@zeuslawyer zeuslawyer left a comment

Choose a reason for hiding this comment

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

Some minor comments/questions.

@cl-sonarqube-production
Copy link

SonarQube Quality Gate

Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

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