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

fix: visual and progress score display enhancement #36203

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

ihor-romaniuk
Copy link
Contributor

Description

This pull request contains styling fixes and display problem score for Problem xblock.

  • [1] Add more space between problem description and options block.
  • [2] Center radio/checkbox button and answer text in options.
  • [3] Display float number in the points score label above the options block (display the floating point number after sending in the same format as when loading the block).

Related Pull Requests

PR to the quince branch: #34861
PR to the redwood branch: #34862

Screenshots before:

[1] image [2] image [3] before submit image [3] after submit image

Screenshots after:

[1] image [2] image [3] before submit image [3] after submit image

Steps to Reproduce:

  1. Enable new video editor and sharing by adding in /admin/waffle/flag/ => new_core_editors.use_new_problem_editor
  2. In studio open unit -> add new component -> Problem -> Single / Multiple select
  3. Check problem displaying

@openedx-webhooks
Copy link

Thanks for the pull request, @ihor-romaniuk!

This repository is currently maintained by @openedx/wg-maintenance-edx-platform.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

  • If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
    • This process (including the steps you'll need to take) is documented here.
  • If it doesn't, simply proceed with the next step.

🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

  • Dependencies

    This PR must be merged before / after / at the same time as ...

  • Blockers

    This PR is waiting for OEP-1234 to be accepted.

  • Timeline information

    This PR must be merged by XX date because ...

  • Partner information

    This is for a course on edx.org.

  • Supporting documentation
  • Relevant Open edX discussion forum threads

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.


Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

  • The size and impact of the changes that it introduces
  • The need for product review
  • Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

@openedx-webhooks openedx-webhooks added the open-source-contribution PR author is not from Axim or 2U label Feb 3, 2025
@ihor-romaniuk
Copy link
Contributor Author

Hello @farhaanbukhsh
Regarding my previously closed PRs #34860
I added missing styles after rebasing, and now my fixes work correctly:

  • [1] (styling) Add more space between problem description and options block.
  • [2] (styling) Center radio/checkbox button and answer text in options.
  • [3] (functionality) Display float number in the points score label above the options block (display the floating point number after sending in the same format as when loading the block).

More details about point [3]:

  • When you load the page, you see the score in format 0.0/1.0 point (ungraded)
image - After you submitting the answer, you score transforms to `0/1 point (ungraded)` or `1/1 point (ungraded)` accordingly. And it transforms float number to integer. image - We fix it and save the float number format after submitting. image

@ihor-romaniuk ihor-romaniuk force-pushed the romaniuk/fix/visual-and-logic-enhancement-for-problems branch from f984a11 to 5e3411a Compare February 4, 2025 08:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
open-source-contribution PR author is not from Axim or 2U
Projects
Status: Needs Triage
Development

Successfully merging this pull request may close these issues.

2 participants