Open ormsbee opened 1 year ago
There was a slack thread about this as well.
Just to be clear @ormsbee , would this DEPR also cover the Matlab API Key field in the problem editor, thus clearing up 2U's T&L team to remove it from the new React-based problem editor? (cc @jristau1984)
@kdmccormick: Yes, but to be clear: I don't think that work needs to wait for this DEPR to be accepted, since it's more of a bookkeeping DEPR–i.e. I'm pretty sure that it's been broken for years, so immediately removing the view of the broken thing doesn't negatively impact users. I'm leaving it open for a couple of weeks of comment Just In Case, and if people want to add any more information.
This DEPR was announced here: https://discuss.openedx.org/t/deprecation-removal-matlab-specific-handling-in-edx-platform/10069/5
Overview
Our system currently has special handling for MATLAB problems via an old integration through xqueue that isn't really supported any longer, and appears to be broken today. Since this integration should now be done via LTI, we can remove:
matlab_api_key
attribute in ProblemBlock, as well as the version defined for inheritance purposes.MatlabInput
coderesponse
and xqueue.This would eliminate the "MATLAB API Key" advanced course setting UI in Studio:
And the equivalent one at the ProblemBlock level:
Effect on old course content:
Proposal Date
10 May 2023
Target Ticket Acceptance Date
24 May 2023
Earliest Open edX Named Release Without This Functionality
Quince.
Since it is not currently in a working state, there's no need to offer an extra release for migration.
Rationale