Fix #17219 Corrected the Fraction output logic

[HardikGoyal2003]

Overview

1. This PR fixes or fixes part of #17219.
2. This PR does the following: Updates the output for fractions in Guppy.

Essential Checklist

• The PR title starts with "Fix #bugnum: " or "Fix part of #bugnum: ...", followed by a short, clear summary of the changes.
• I have followed the build process and "verifying your changes" section mentioned in the readme file.
• I have followed the instructions for making a code change.
• I have assigned the correct reviewers to this PR (or will leave a comment with the phrase "@{{reviewer_username}} PTAL" if I don't have permissions to assign reviewers directly).
• The linter/Karma presubmit checks pass on my local machine, and my PR follows the coding style guide).
• "Allow edits from maintainers" is checked. (See here for instructions on how to enable it.)

Proof that changes are correct

Screencast.from.02-03-24.12.21.14.AM.IST.webm

PR Pointers

• Never force push! If you do, your PR will be closed.
• To reply to reviewers, follow these instructions: https://github.com/oppia/oppia/wiki/Make-a-pull-request#step-5-address-review-comments-until-all-reviewers-approve
• Some e2e tests are flaky, and can fail for reasons unrelated to your PR. We are working on fixing this, but in the meantime, if you need to restart the tests, please check the "If your build fails" wiki page.
• See the Code Owner's wiki page for what code owners will expect.

[HardikGoyal2003]

@seanlip PTAL! Thanks!

[seanlip]

@HardikGoyal2003 Which code am I actually supposed to review here? I don't see the source file(s) from which all these builds were generated, and I also don't understand why this has changed so much from the master branch. Could you please explain?

[HardikGoyal2003]

@HardikGoyal2003 Which code am I actually supposed to review here? I don't see the source file(s) from which all these builds were generated, and I also don't understand why this has changed so much from the master branch. Could you please explain?

@seanlip I analysed and what I found is:

• on running $ npm test it creates the hash changes in all files in coverage folder which is just to test and check test coverage.
• Using build command doesn't make any changes in min.js file, hence we need to do it manually.
• if we are changing the source files and keeping min.js file unchanged then no changes will be reflected on localhost, therefore localhost depends on min.js file.
• if we change src file then run build command other files also gets updated but min.js file is constant.

Thanks!

[HardikGoyal2003]

@seanlip PTAL! I have reverted the last commit and now test command has not been run but build command has been run and min.js has been edited manually. Thanks

[seanlip]

@HardikGoyal2003 This is a concern IMO. We need a standard build process that also updates the min.js file, and this should be documented in the PR template etc. What should that process be? What does the guppy project itself usually use?

("Manual changes" isn't an acceptable answer.)