You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the addition of both a privateCache (per script identifier, useful for sharing timers) and a sharedCache (shared across all scripts from all languages) in openhab/openhab-core#2887, we have to update our implementation of cache.
Backward compatibility must be kept!!
After we have a solution here, we can remove the SharedCache from JS Scripting.
My proposal is:
for the current methods of cache:
check if the new caches from core are available
if they are available, log a deprecation warning and use the shared cache from core instead of the addon‘s shared cache implementation so that we can remove SharedCache from the addon
if they are not available (means the library runs on an „old“ openHAB version), do nothing and keep the current behaviour
add a private property to cache to allow access to the private cache
add a shared property to cache to allow access to the shared cache
With the addition of both a
privateCache
(per script identifier, useful for sharing timers) and asharedCache
(shared across all scripts from all languages) in openhab/openhab-core#2887, we have to update our implementation ofcache
.Backward compatibility must be kept!!
After we have a solution here, we can remove the SharedCache from JS Scripting.
My proposal is:
cache
:private
property tocache
to allow access to the private cacheshared
property tocache
to allow access to the shared cache@rkoshak @digitaldan @jpg0 WDYT?
The text was updated successfully, but these errors were encountered: