Issues #101, #102, #103, #104 #105
Open
+136
−30
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
added 3 commits
April 27, 2020 15:33
… IoT systems Update the documentation and Tests, too Bug: adding the spec, and missing comma to the documentation
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 pull request will solve the following issues:
#101 timestamp documentation is not correct -> corrected
#102 timestamp $unix as inputFormat with integer value as value is not working ->
now integer values are accepted in the value transformer.
#103 timestamp $unix as output format will create quoted integer value -> $unix (and $unixext) will now create JSON integer as output format value
#104 Feature: timestamp operation $unix with milli second support ->
i introduce the $unixext format as input and output parameter for processing unix timestamps as millis from epoche. Adding tests for $unixext, too.