-
Notifications
You must be signed in to change notification settings - Fork 357
WIP - Remove renderer's deprecated getUserInput in favor of the preferred getUserInputMap #2590
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
base: main
Are you sure you want to change the base?
Conversation
…UserInputMap Also removes a test that was testing the deprecated functionality
…ecated array version of user input with preferred object version
Size Change: -49 B (-0.01%) Total Size: 472 kB
ℹ️ View Unchanged
|
"@khanacademy/perseus": major | ||
--- | ||
|
||
Replace deprecated array format of user input with preferred object format to consolidate the user input types. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am pretty sure this is a major change, but not sure if I need to add more information to the changelog. I add more details in the PR summary, so not sure.
npm Snapshot: PublishedGood news!! We've packaged up the latest commit from this PR (21cbbdb) and published it to npm. You Example: pnpm add @khanacademy/perseus@PR2590 If you are working in Khan Academy's frontend, you can run the below command. ./tools/bump_perseus_version.js -t PR2590 If you are working in Khan Academy's webapp, you can run the below command. ./dev/tools/bump_perseus_version.js -s n -t PR2590 |
a45d3b8
to
68a6c2d
Compare
…ngly unneeded code
Summary:
Renderer currently has two methods for getting user input: the deprecated method getUserInput which returns an array of type UserInputArray and the preferred getUserInputMap which returns an object of type UserInputMap. The object type is the preferred format going forward and is currently used in scoring and will be used in scoring via the new Perseus service.
To remove the deprecated method, we replace all uses of it in Perseus with the preferred method and then delete tests and comments related to the deprecated method. This change will require some coordination with other teams that rely on this functionality outside of Perseus and most likely updates to where user input is consumed. Testing will take place to determine the necessary places that require updates.
Issue: LEMS-2523
Test plan:
--- Use the tests to update all usages until all tests pass