-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Let rulesets store information in established subscriptions #618
Comments
Playing with this candidate rule:
|
Have had success with this rule, testing in
|
Rather than modifying the It would also be important to then clean up the layered-on map by selecting when these
|
Proposing a rule that selects on a
wrangler:new_key_value_pair
event, with attributes:Id
the established subscription identifier,key
a key not reserved* for subscriptions, andvalue
an optional value (a falsy value to mean remove the key).The rule to raise a
wrangler:key_value_updated
event upon successful addition/deletion to/from the established subscription, with the original attributes.The key-value pair is for the use of the pico that sets it.
For keys that begin either "Rx_" or "Tx_", it is considered good relationship practice to also send a similar event over the subscription to the other side, with the key prefix reversed. Care must be taken to avoid initiating an infinite loop.
*Reserved subscription keys are:
The text was updated successfully, but these errors were encountered: