source-academy / py-slang / 31261099111

86%

push

github

Stepper: honor the host-configured step limit instead of a hardcoded 1000 (#427)

* Stepper: honor the host-configured step limit instead of a hardcoded 1000

The CSE machine tab already reads its snapshot cap from the host's
/__cse_config__ file (the frontend's "Step Limit" control), but the
Stepper tab fetched that same config only for breakpoint lines and
silently ignored config.stepLimit, always stepping with a hardcoded
default of 1000 regardless of what the user configured.

PythonStepperRunnerPlugin gains a setStepLimit() method; PyStepperEvaluator
now calls it with the fetched config.stepLimit before stepping, once the
frontend actually starts sending it (a separate, paired change extends the
Step Limit control's visibility to Python chapters).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018H2DBHvhZY3xQFoUGHXuHZ

* Stepper: guard against undefined markers in stepLimit test

Casting s.markers to an array doesn't make undefined iterable, so
.map would throw for a step without markers. Every other markers
usage in the codebase treats it as optional (markers?.[0]).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Ry6yXg5XMfquAzmCR8ysNL

---------

Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>

4822 of 6014 branches covered (80.18%)

Branch coverage included in aggregate %.

3 of 3 new or added lines in 2 files covered. (100.0%)

10772 of 12020 relevant lines covered (89.62%)

164318.09 hits per line