Decorator

[jgab 2,647]

Here is an example of adding "decorators" to functions in QuickApps.

Please login or register to see this attachment.

It's similar to the model, ex,

Please login or register to see this link.

- but of course adopted to the limitations we have in QA/Lua...

The implementation consists of a QA file "Decorator" and a couple of QA files for decorator plugins for different decorations.

When the QA starts up, the decorator parses all QA files and detects function decorations and calls relevant plugin.

Ex.

Please login or register to see this code.

 

results in

Please login or register to see this code.

 

Another decorator is to declare functions to receieve sourceTriggers

Please login or register to see this code.

The names of the function parameters are important as the function will get the event key corresponding to its parameter name.

In this case the 'value' key of the event. 

If we declared function QuickApp:stateChange(id,value) it would have received the id and the value key of the event.

The special parameter '_event' will receive the full event structure.

It's a little bit more limited compared to my previous EventLib but easier to use.

 

A third decorator, Private, is to declare QuickApp functions "private", meaning they can't be invoked remotely with a fibaro.call(....)

Please login or register to see this code.

Here we see also that we can combine decorators...

 

The concept is still under development, the plugins above works, and I've started to use it and it seems useful/easy to use.

Could probably be useful with a type-check decorator...

Edited October 24, 2024 by jgab