-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comment Question parsing #206
Comments
Separate from #205? |
Yeah #205 is for the survey but this is for the on-page comments. Maybe they can be wrapped into one... |
Maybe but not necessarily. I was genuinely wondering. Perhaps keeping them apart is simpler. |
It probably is, that way people can say "I've done these ones" with distinct names instead of names not directly infering what they do: |
Yep this could work. Folder per page containing a file for each fragment comment, and a file for each commentquestion, one line per subject. Should be an incremental change to the commentparser. |
No parsing yet for the on-page custom comment-question nodes.
A file structure may follow something like:
Each csv should have the file-save name followed by the result type for each node. This will allow for multi-entry data types (such as the checkbox and radio) to be contained in the same scope as the single entry (question, number or slider).
The text was updated successfully, but these errors were encountered: