LExSIS Documentation

[alfredats]

Tracker for updating the following:

1. adding screenshots to illustrate how using the ask/any/another headers modify the UI
2. adding more examples (perhaps having an initial example, broken down into pieces in each section would help better?)

[alfredats]

Based on previous comments by Avishkar, I've decided to use the rock-paper-scissors scenario as an example for the documentation. The aim here is to use the example to showcase the differences in how the UI would behave based on changes to certain headers.

A draft RPS lexsis file & sCASP file have been written, but it seems like the interview generator in l4-docassemble doesn't like whatever has been written.

At this point I will be focused on troubleshooting the sCASP file, because it is the format that is less familiar to me.

[alfredats]

Some changes have been made to the sCASP file, and progress has been made.

Right now, the interview generation still fails, but a new error appears:

Scouring the docassemble-l4 repository for new_list points me to a find_relevant function within intgen.py:

It's used within generate_agendas in the same file, which makes me think that my lexsis encoding is now the culprit of the error. Will take a look at it again tomorrow during the morning pair programming session with Ruslan.

[alfredats]

During the pair programming session, @kharus and I managed to fix the error listed above, but it only gave birth to another. He then pointed out that the docassemble-l4 repo is in desperate need of a test suite to ensure proper coverage of cases.

See smucclaw/docassemble-l4#14