Other values than numbers?

[trygve-lie]

I'm not 100% into the definition of "Telemetry" so this might break the purpose of this module, but is there any reason why just Numbers are accepted as values?

Is there any reason to not allowing the value be anything like a String or a JSON?

If only Numbers should be accepted I think the there should be a check for the input value should be done and not just converting the stored String to a Number on retrieval.

[binocarlos]

It's a great point - there is no reason for the values to just be numbers - other than I had speed, temperature etc in my head when I wrote it.

I've added you as a collaborator, it would be great if you take a look at this - I've not started using lem in anger yet so a breaking change (i.e. bump to 2.x.x) would be fine.

I think the only part that is important to be a number is the time-stamp part of the key but in my book telemetry is any value against a time-stamp so yes string values are equal citizens :)

Perhaps valuestream could accept a third argument that is a function that allows for the conversion of the value into a number rather than assume its supposed to be a number?

[trygve-lie]

Sorry for my delayed reply. I've been a bit busy.

Thanks for adding me as a collaborator and I sure can look at this. I have a project where I think this module will fit perfectly if it can store objects. I'll start looking into this in a couple of days.

[binocarlos]

Good stuff thanks :)

I've just hit another use case which is a simple event log (in my case for logging user actions) and the data would be a JSON string so this is definitely a good idea.