This repository was archived by the owner on Dec 18, 2024. It is now read-only.
Feature/native datatypes in VSS database #293
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
Signed-off-by: Sebastian Schildt <sebastian.schildt@de.bosch.com>
Defaults to string for all non-GRPC connections (Websockets, HTTP) Signed-off-by: Sebastian Schildt <sebastian.schildt@de.bosch.com>
Signed-off-by: Sebastian Schildt <sebastian.schildt@de.bosch.com>
# for free
to subscribe to this conversation on GitHub.
Already have an account?
#.
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.
A first try migrating VSSDatabase to native types: Data coming from Websocket VISS (as string) will be stored as VSS native datatype (int, float, etc...)
getSignal in VSSDatabase has an optional parameter to decide whether all outputs should be converted to string (as needed for VISS), or kept as native.
Please take a look @nayakned
I did not yet adapt the return type from string to jsoncons.... That will be another PR