[Test failure] TC_AUTHOR_50: Numerical input component generates an error with the formula shown in the usage example.

[DeimerM]

Release

Sumac

Expected behavior

It is required that when the example formula is entered into the numerical input component, it should render without any errors.

Actual behavior

When a numeric component is added, and the formula shown in the example is entered m*c^2, an error occurs

Steps to reproduce

1. Add a numerical input component.
2. Enter the formula shown in the example: m*c^2.
3. Observe the error.

Additional information

Error obtained:

Example:

[mariajgrimaldi]

@DonatoBD: have you had a chance to triage this? Let me know!

[pdpinch]

I'll take a look into this, but I think the issue is that the sample problem is incomplete. If I recall correctly, the problem needs to define variables like m and c in order for the learner submission to work.

[DonatoBD]

Hi, as @pdpinch mentioned, the answer's value should include integers, fractions, and constants. The formula works correctly in nutmeg (without mfe), but it doesn't work in redwood (with mfe enabled).

I'm not very sure about the constants, but I'm reviewing 'Completing Mathematical and Scientific Assignments' to see if it's a configuration issue with the component or an error with the constants we've had for a long time.

[DonatoBD]

Well, this is kinda interesting. Comparing it to nutmeg (without mfe), I could see that the olx of the "numerical input" problems adapts depending on the answer.

When we put "m*c^2" and see the olx, it's created as a "stringresponse", while if we put "10" it creates it as a "numericalresponse".

However, in the mfe of course-authoring, the template for each problem is already defined, and the numerical input only uses "numericalresponse".

For the case of defining variables, there's the advanced problem of "math expressions", which uses "formularesponse".

This makes me think that this case has been happening since the new component editors were activated with the mfe. I don't know if we should open an issue in course-authoring so that the creation of the olx for numerical input adapts the same as before, or on the contrary, pass it to the product to see if they want to stick to the premise that it only accepts integers and for everything else, use another type of component

cc @mariajgrimaldi

[pdpinch]

Great find! You've reminded me why we still haven't committed to using the new problem editors.

[mariajgrimaldi]

@DonatoBD: I agree we should open the issue in the course authoring MFE and discuss what can do to move this forward there. What do you think?