mjhjmtu

I am trying out l3keys for the first time and I am encountering the following issue. I have some boolean keys (true/false). For them it looks nice to use .bool_set:N so that I can get automatic validation of the value passed into the key and I also get the key value nicely stored in a boolean variable for later inspection.

At the same time, I would like to execute some code right after the variable is set. However, it looks like .code:n and bool_set:N cannot be used together on the same key, because the one that comes later substitutes the action of the first. In practice, there seems to be no possibility to run a hook triggered by the variable setting action.

Obviously, there are several possible workarounds:

• run some code after every key_set:nn.
  
  However, this means that such code needs to check for every possible variable being set to see if it has changed and take action accordingly. If you have say 30 variables, this means checking all of them, when maybe only one of them is being changed. Having a hook invoked just for the variable that has been set seems more appropriate as long as the variables do not interact one with the other.




• use .code:n instead of the variable setting actions.
  
  However, this means redoing the parsing and validation of the value.

Because all the workarounds seem to have inefficiencies of their own, I wonder if I am missing something... Any help is appreciated!

This is not a real solution, more like a viable workaround:

You could create a .meta:n key, that is the documented front-facing key, and two additional keys, one for the .bool_set:N, and one for the .code:n:

documentclassarticle

usepackagexparse
ExplSyntaxOn
keys_define:nn Callegar 
 
 my-bool .meta:n = my-bool-bool = #1 , my-bool-code = #1 ,
 my-bool-bool .bool_set:N = l_Callegar_bool,
 my-bool-code .code:n =
 Execute~Some~Code~for~bool_if:NTF l_Callegar_bool true false 
 
NewDocumentCommand setmykeys m 
 
 keys_set:nn Callegar #1 
 
ExplSyntaxOff

begindocument
setmykeysmy-bool=true
enddocument

The following redefines an internal function of the l3keys module and might therefore break stuff in the future. Use with caution.

After digging a bit through the l3keys code, I thought one could add a hook to the keys. The following does so by adding a hook mechanism to __keys_cmd_set:nn. After that one can define a hook with:

keys_define:nn <module> <key> .hook:n = <hook code> 

I didn't test it thoroughly, but as far as a quick view l3keys could tell, the hook mechanism should work with any key type. Note that it doesn't create any key on its own, so you have to use it on an already defined key.

documentclassarticle

usepackagexparse
ExplSyntaxOn
% redefine a part of the internals of l3keys
cs_set_protected:Npn __keys_cmd_set:nn #1#2
 
 cs_set_protected:cpn c__keys_code_root_tl #1 ##1
 #2 use:c c__keys_code_root_tl #1 _hook 
 
% add the .hook:n type
cs_new_protected:cpn c__keys_props_root_tl .hook:n #1
 
 tl_gset:cn c__keys_code_root_tl l_keys_path_tl _hook #1 
 

keys_define:nn Callegar 
 
 my-fool .bool_set:N = l_Callegar_bool,
 my-fool .hook:n = Execute~Some~Code~Regardless ,
 my-fool / true .hook:n =
 Execute~Some~Hook~Code~for~true ,
 my-fool / false .hook:n =
 Execute~Some~Hook~Code~for~false ,
 
NewDocumentCommand setmykeys m 
 
 keys_set:nn Callegar #1 
 
ExplSyntaxOff

begindocument
setmykeysmy-fool=true

setmykeysmy-fool=false
enddocument

A slightly different implementation that also allows .hook:n to access the value:

cs_set_protected:Npn __keys_cmd_set:nn #1#2
 
 cs_set_protected:cpn c__keys_code_root_tl #1 ##1
 
 #2
 cs_if_exist_use:cT c__keys_code_root_tl #1 _hook ##1 
 
 
% add the .hook:n type
cs_new_protected:cpn c__keys_props_root_tl .hook:n #1
 
 cs_set:cpn c__keys_code_root_tl l_keys_path_tl _hook ##1 #1 
 

keys_define:nn Callegar 
 
 my-fool .bool_set:N = l_Callegar_bool,
 my-fool .hook:n = Execute~Some~Code~Regardless~'#1' ,
 my-fool / true .hook:n =
 Execute~Some~Hook~Code~for~true ,
 my-fool / false .hook:n =
 Execute~Some~Hook~Code~for~false ,