There was a report on L5.P2 where the student has to code a function named draw_three_squares() and they used the number 3 instead in the name. There are a bunch of exercises like these where we need them to create a function or define a specific symbol.
We should have a general purpose library function we can use as a pre-requisite check for practices. We could then use it with a generic help message from relevant practices to tell students when they need to define a function named in a specific way.
In general, I'd like to bring in the same notion of requirements as we have in GDPractice.
This should be implemented first and then applied to relevant practices.
Note that this should probably be two things. On the one hand, a way to check for prerequisites in a practice, and on the other hand, a library function to verify that a symbol is defined. So, for example, that there is a function with a certain name in the code. And the prerequisite checks can check anything.
There was a report on L5.P2 where the student has to code a function named
draw_three_squares()and they used the number 3 instead in the name. There are a bunch of exercises like these where we need them to create a function or define a specific symbol.We should have a general purpose library function we can use as a pre-requisite check for practices. We could then use it with a generic help message from relevant practices to tell students when they need to define a function named in a specific way.
In general, I'd like to bring in the same notion of requirements as we have in GDPractice.
This should be implemented first and then applied to relevant practices.
Note that this should probably be two things. On the one hand, a way to check for prerequisites in a practice, and on the other hand, a library function to verify that a symbol is defined. So, for example, that there is a function with a certain name in the code. And the prerequisite checks can check anything.