oracle-samples/clara-rules

Consider whether to remove :original-constraints from conditions in session inspection

Opened this issue · 0 comments

The conditions returned to the user by session inspection can contain the :original-constraints key specified in this schema which contains the value of the :constraints key as provided to the compiler, while the :constraints key itself has a subset of its original contents. This seems like an implementation detail from the POV of session inspection that shouldn't be exposed to the user. It seems to me like the least surprising behavior for users would be to be able to use the same data they provided to the Clara compiler to index into the various data structures returned by session inspection. I'm envisioning applying a fix like this to the data returned to the user.

Thoughts?