Allow exposes in ModernExtend interface to be a function

[burmistrzak]

Already works in Definition, now it does in ModernExtend as well!

Context here: #7444 (comment)

[burmistrzak]

@Koenkk Huh, that's interesting...
Why doesn't this just work? I guess, because some libs are expecting Expose[]? 🤔

[burmistrzak]

@Koenkk Hmm, we still have some type mismatches here and there...
Maybe there's actually a good reason why modernExtend only uses Expose[], that I'm simply not aware of?

We don't necessarily have to change the interface, IMHO.
As long as we somehow figure out how to dynamically update exposes in a ModernExtend based on Zh.Device stuff, I'll finally be able to finish up the conversion of the BMCT-SLZ. 😊

[Koenkk]

I've implemented it in 059dfb8 now, so this can be closed.

[burmistrzak]

@Koenkk Oh nice, thank you! ☺️
I would have made the required changes myself, but I first wanted to make sure there're be no sneaky surprises. Glad you've figured it out.

[burmistrzak]

@Koenkk What do you think, did I get that exposes right? Do I need some additional arguments somewhere? 🤔

bmct: (): ModernExtend => {
    const fromZigbee: Fz.Converter[] = [
        // ...
    ];
    const toZigbee: Tz.Converter[] = [
        // ...
    ];
    const exposes: DefinitionExposesFunction[] = [
        (device: Device, options: KeyValue): Expose[] => {
            const expose: Expose[] = [
                e.linkquality(),
            ];
            // Doesn't use 'device' yet, but you get the idea.
            return expose;
        },
    ];
    return {
        fromZigbee,
        toZigbee,
        exposes,
        isModernExtend: true,
    };
},

[Koenkk]

Yes this looks good, does it work?

[burmistrzak]

Yes this looks good, does it work?

@Koenkk We'll know soon enough!
Just have to reset a BMCT-SLZ first. Hopefully the Expose[] gets updated correctly. 🤞