defsub and entities both get rewritten into multiple rules. With explanations, we currently end up showing the rewritten rules instead of the ones the user actually wrote. There's a long commented out section in the event-parser ns where I'm trying to work this out. It's doable but a bit tricky.
It's not clear #26 would help since AFAICT we'd still receive the split rules in the event data. Trying to sort this out on the sending end would only be advantageous if we could figure out how to get a clean mapping for these rules early on ... by the time the event data is received in the listeners layer we're basically looking at the same problem on the sending end as the receiving end.
defsub
andentities
both get rewritten into multiple rules. With explanations, we currently end up showing the rewritten rules instead of the ones the user actually wrote. There's a long commented out section in the event-parser ns where I'm trying to work this out. It's doable but a bit tricky.It's not clear #26 would help since AFAICT we'd still receive the split rules in the event data. Trying to sort this out on the sending end would only be advantageous if we could figure out how to get a clean mapping for these rules early on ... by the time the event data is received in the listeners layer we're basically looking at the same problem on the sending end as the receiving end.