There isn't any enforcement in the shared variables system that the value received is actually matches the type definitions that are declared. The easiest path to resolving this would be finding a way to integrate ts-runtime-checks.
In theory... should be able to take the provided type definitions from the user, convert those to a validation function (pre-compute), then use that logic to validate every set
📬 Caveats
Maybe as a strict mode? Unclear on the level of overlap with just regular type checking being used to block the code from running in the first place.
🪤 Context
There isn't any enforcement in the shared variables system that the value received is actually matches the type definitions that are declared. The easiest path to resolving this would be finding a way to integrate
ts-runtime-checks
.In theory... should be able to take the provided type definitions from the user, convert those to a validation function (pre-compute), then use that logic to validate every set
📬 Caveats
Maybe as a strict mode? Unclear on the level of overlap with just regular type checking being used to block the code from running in the first place.
idea pile item