source-academy / js-slang / 35714387614

86%

push

github

Rename displayed language name from Source to JavaScript (#2092)

* rename displayed language name from Source to JavaScript

Renames the student-facing language name from "Source §1-4" to
"JavaScript §1-4" throughout: error/rule message text (noNull,
noDotAbbreviation, modules/errors.ts), docs/lib jsdoc prose, the
top-level README, and the whole docs/specs LaTeX spec corpus and
docs.sourceacademy.org site generator for the four default chapters.

Internal identifiers stay unchanged (SourceEvaluator, the Chapter enum,
sourceLanguages, etc.) - this is a display-string rename only, matching
how source-academy/language-directory#65 already renamed the frontend's
language picker.

## docs/specs (PDFs)

New javascript_1..4.tex are the real, renamed entry points (built via
`docs/specs/Makefile`, now listing them alongside the existing SPECS).
source_1..4.tex become one-line `\input javascript_N.tex` shims, kept
only so the historical source_N.pdf URLs keep resolving - their content
already reads "JavaScript §N" since the shared \input'd body files
(source_intro.tex, source_typing.tex, source_return.tex, etc.) were
renamed directly. source_js_differences.tex ("Deviations from
JavaScript") needed care since both sides of that comparison would
otherwise read "JavaScript" - it now says "this sublanguage" for the
restricted variant and "full JavaScript"/"a full JavaScript
implementation" for the real language, avoiding the collision.
Deprecated variants (Typed/WASM/Explicit-Control/Stepper/Type
Inference) are out of scope and keep the "Source §N ..." name; only
their cross-references *to* the renamed base chapters were updated.

## docs/source (the jsdoc-generated site)

scripts/docs.mjs gets four new build targets (dst: 'javascript_N/'),
reusing the same READMEs as the existing source_N/ targets - same
"content already renamed, folder kept for compat" pattern as the PDFs.
This surfaced a real bug in the shared jsdoc template
(docs/jsdoc/templates/template/publi... (continued)

2517 of 3052 branches covered (82.47%)

Branch coverage included in aggregate %.

1 of 3 new or added lines in 3 files covered. (33.33%)

4915 of 5622 relevant lines covered (87.42%)

352267.98 hits per line