Skip to content

Model the fields of a real Lambda Feedback export - #90

Draft
peterbjohnson wants to merge 1 commit into
mainfrom
model-fields
Draft

peterbjohnson wants to merge 1 commit into
mainfrom
model-fields

Conversation

@peterbjohnson

Copy link
Copy Markdown
Member

Updates to include more components of the Lambda Feedback content model:

  • response areas
  • structured tutorial
  • worked solution branching
  • some parameters (hiddenAt, etc.)

Also renames 'main text' as 'master content' to match Lambda Feedback. This leads to a larger diff, but now seems as good a time as any to make that change.

Breaking: Question.main_text is now master_content and Part.text is now content.

Tests compare the keys written with those of real exports, including each response type's config.

The code was generated by Claude 'directly', not by an orchestrator. I reviewed every line, and re-wrote all the docstrings myself. I haven't looked closely at the tests, that needs a stronger review.

A part gains response areas, a final answer, a structured tutorial and
titled branches for its tutorial and worked solution. A question gains its
settings, and a set gains isSurvey, releasedAt, hiddenAt, manuallyHidden and
chatbotVisibility. Each response type is a subclass of ResponseArea holding
the settings and answer shape of the platform's schema; cases take a colour
and answer boxes a check button label.

Breaking: Question.main_text is now master_content and Part.text is now
content, matching Lambda Feedback's names.

Tests compare the keys written with those of real exports, including each
response type's config.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant