RunestoneInteractive / RunestoneInteractive/rs

Problem report: https://runestone.academy/ns/books/published/csawesome2/topic-1-9-method-signatures.html

Open Beginner friendly
#1,516 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Content
Dominant language
TypeScript
Stars
69
Forks
117
Avg merge
6d 4h
Merged PRs (30d)
24

Description

A problem was reported through the Runestone "Report a Problem" form.

Field Value
Reporter ZitongYe
Email yztwnx@gmail.com
Course CSAwesome2
Page https://runestone.academy/ns/books/published/csawesome2/topic-1-9-method-signatures.html
Reported at 2026-09-16T03:08:46.842335
Description

This is not a bug in the code. This is a problem with the course content presentation. I think you should use the verse method as an example when initially introducing the method signature and method heading. Using println as an example makes it confusing because you haven't introduced overloading yet.

Browser console log
[log] Timezone cookie matches, not sending timezone to server
[log] This page served by undefined
[log] setup navbar for logged out
[log] triggering runestone:pre-login-complete
[log] Runestone pre-login complete
[warn] No ads to show.
[log] adding video popouts
[log] setting up pretext

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the reported CSAwesome2 page, topic-1-9-method-signatures.html, and inspect the introduction to method signatures and method headings. Done means the introductory example uses the verse method rather than println, so the explanation is clear before overloading is introduced.

Written by the indexing model from the issue text.

Assessment

Domain
content, documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
72/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.