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.
I had the type conflict issues for numbers.
Both the:
InfluxDB (v2) sets the type int or float for a specific field based on the data first written (to a shard(!) impossible to control) and since javascript/typescript both input values 1.0 and 1 are Number.isInteger == true, then it's only a matter of time before a subsequent write fails in the above mentioned errors.
An old InfluxDB discussion (2015) suggest always writing numbers as floats (except for the timestamp), so this PR suggests doing the same in the n8n-nodes-influxdb-package.