Add JSON-Function for Templates #242
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Neat! Makes me want to rethink the way we handle JSON in the HttpBee. |
|
I think |
Ok, no problem. I'm fine with both |
Mark-Jung
pushed a commit
to Mark-Jung/beehive
that referenced
this pull request
May 15, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds a json-Function to be used in String-Templates. In my Use-Case I serialize an entire Event and provide the Json-Document as Input to the ExecBee for further processing like this:
{{.|Json}}I was not sure about the casing of "Json". I decided to go with that because it is easier to type and fits the existing functions. But technically it would be JSON.