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.

Sign up for GitHub

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

Jump to bottom

eval: add fn::from{Base64,JSON} #117

Merged
merged 1 commit into from
Oct 13, 2023
Merged

eval: add fn::from{Base64,JSON} #117

merged 1 commit into from
Oct 13, 2023

Conversation

pgavlin
Copy link
Member

@pgavlin pgavlin commented Oct 13, 2023

These changes add two new builtins, fn::fromBase64 and fn::fromJSON. The former decodes a base64-encoded string into a binary string and the latter decodes a JSON string into a value.

Fixes #103.
Fixes #104.

@pgavlin
eval: add fn::from{Base64,JSON}
13eff77 
These changes add two new builtins, `fn::fromBase64` and `fn::fromJSON`.
The former decodes a base64-encoded string into a binary string and the
latter decodes a JSON string into a value.

Fixes #103.
Fixes #104.
@pgavlin
Copy link
Member Author

pgavlin commented Oct 13, 2023

helps to add all the files 🤦

@pgavlin pgavlin merged commit 41271a0 into main Oct 13, 2023
@pgavlin pgavlin deleted the pgavlin/decoders branch October 13, 2023 21:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@komalali komalali komalali approved these changes

@cleverguy25 cleverguy25 Awaiting requested review from cleverguy25

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

consider adding a fromBase64 function consider adding a fromJSON function
2 participants
@pgavlin @komalali