Teacher tool: Initial validation logic

[kimprice]

Big thanks to @thsparks for helping me get this set up.

Currently, the validation works for BlockCheckCriteria only. It takes the rubric and sets the required block counts for each block id. Then it runs the validateBlocksExist function for each set of blocks in the rubric.

Upload target: https://arcade.makecode.com/app/5df94cd2b924c898ff9960973789eff8048cc4c5-2776605799--eval
Sample share link: https://arcade.makecode.com/S42128-59682-77192-60950
Sample rubric:

{
    "criteria": [
        {
            "displayText": "One or more custom functions that must be called",
            "criteriaId": "blockCheck",
            "blockRequirements": [
                {
                    "blocks": ["function_call", "function_call_output"],
                    "count": 1
                },
                {
                    "blocks": ["function_def"],
                    "count": 1
                }
            ]
        },
        {
            "displayText": "Two different kinds of loops used",
            "criteriaId": "blockCheck",
            "blockRequirements": [
                {
                    "blocks": ["controls_repeat_ext", "device_while", "pxt_controls_for", "pxt_controls_for_of"],
                    "count": 2
                }
            ]
        }
    ]
}

[eanders-ms]

Looks good!

[thsparks]

I wonder if we should just throw an error in this case rather than switch to blocks. Having that switch be a side-effect of another call feels like it could lead to some unwanted behavior...plus, if we throw an error instead of switching, this function doesn't have to be async :)

[kimprice]

Good point!

[thsparks]

One thought about perhaps throwing an error rather than having a switch-to-blocks side effect on that getBlocksAsync call. Otherwise LGTM!

[thsparks]

👍