The code structure has gotten more complicated than it is reasonable to try and solve with the s(CASP) NLG method.
What we need to do is take some of the work that is currently happening inside the scenario editor javascript code to recursively generate natural language representations of terms, and move that onto the server, and provide that as the human tree-based structure for the explanation instead of what s(CASP) is generating now. We can then also dramatically simplify the code generation for attribute and category blocks. Scenario editor can continue to generate paragraphs from the raw data, but test editor's tree structure will be immensely easier to read.
The code structure has gotten more complicated than it is reasonable to try and solve with the s(CASP) NLG method.
What we need to do is take some of the work that is currently happening inside the scenario editor javascript code to recursively generate natural language representations of terms, and move that onto the server, and provide that as the human tree-based structure for the explanation instead of what s(CASP) is generating now. We can then also dramatically simplify the code generation for attribute and category blocks. Scenario editor can continue to generate paragraphs from the raw data, but test editor's tree structure will be immensely easier to read.