search

Lexpedite / blawx

A user-friendly web-based tool for Rules as Code.
MIT License
105 stars 9 forks source link

Various constructs not appearing in explanations #415

Closed Gauntlet173 closed 1 year ago

Gauntlet173 commented 1 year ago

I don't know when the behaviour began, but as of now there are a number of language constructs that do not show up in explanations. Logical disequality, numerical constraints, and logical (known false) negation do not seem to generate lines in the explanation tree.

Once that problem is fixed, we will need to update the Scenario Editor to be able to display those lines of explanation properly.

Gauntlet173 commented 1 year ago

Logical negation is resolved in 1.4.1-alpha. The others might still be an issue.

Gauntlet173 commented 1 year ago

Numerical constraints do not appear in the raw explanations generated by s(CASP). Will need to confer with the s(CASP) people to see why that is.

Gauntlet173 commented 1 year ago

Disunities also do not appear in s(CASP) explanations. I have followed up with the s(CASP) developers.

Gauntlet173 commented 1 year ago

s(CASP) developers are looking into it.

Gauntlet173 commented 1 year ago

No word, yet.

Gauntlet173 commented 1 year ago

Again, not going to wait on them any longer. The work-around is wrapper predicates with #pred definitions and changes to the scenario editor code (or if we do it after we server-side the NLG, just once.

Gauntlet173 commented 1 year ago

The solution to this problem is to add a blawx predicate for each of them that doesn't display properly, add #pred statements to the standard code for each of those statements, add code the passes the predicate through to the actual thing, update the scenario editor to display those statements, and update the code generation to use them instead of the originals,

Gauntlet173 commented 1 year ago

Resolved in v1.6.12-alpha