Skip to content
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

Chore/mcq variants api #290

Open
wants to merge 4 commits into
base: beta-1
Choose a base branch
from
Open

Conversation

sukanyamohanty143
Copy link
Collaborator

  1. Add new variants to the existing quiz.
  2. Add new quiz along with its variants.
  3. Add new variants to existing quiz, which already has multiple variants.
  4. Get quiz details along with its all variants if variants exist.
  5. Delete specific variant of a particular mcq/quiz.
  6. Delete quiz and all its variants.
  7. Delete multiple quiz and its variants.
  8. Edit many quizzes, edit quiz and its variant,edit multiple/specific variants of a quiz

{
"key": "fbh77",
"text": "What is Python",
"type": "unstyled",
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are we storing the values for type, depth, inline style ranges, entity ranges, and data?
@sukanyamohanty143 @Arunesh700

id: serial('id').primaryKey().notNull(),
quizId: integer('quiz_id').references(() => zuvyModuleQuiz.id), // Foreign key to main quiz
variantNumber: integer('variant_number').notNull(), // The variant number
question: jsonb('question'),
Copy link
Collaborator

@giribabu22 giribabu22 Oct 17, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why are we storing the question in both tables if it is a variant? @Arunesh700

@@ -411,12 +425,23 @@ export class ContentController {
}

@Post('/editquiz')
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please change it to use the PUT API.

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.

2 participants