Closed ChristopherChudzicki closed 6 years ago
Ok. At some point, I'm going to go through the entire apparatus and figure out just how our error handling is working...
I was planning to tackle #75 next, but you can do it if you want :)
Nope, by all means, all yours!
Ah, that's a very good point. I don't think it will actually be a very big refactoring, though :)
Well, I completely overhauled the bracket balancing and the error messages. Now students see things like this:
Also addresses #82
This is really pretty. Good job!
Resolves #82.
Fixed the typos :)
You obviously had fun writing this. It's very cute :-) Two minor typos.
It was fun :) and the deeply nested for / if's in my earlier approach were driving me nuts.
A FILO stack is definitely the way to do this. You made it much prettier than I would've though!
Resolves #73.
Note that I moved all unmatched parens/brackets tests to
test_calc.py
and out of FormulaGrader. Previously, i understand placing that test intest_formulagrader.py
in order to make sure that the correct error messages actual make it through to the student. Not, I'd rather put tests closer to their source code and test that they raiseStudentFacingError
s.