Hidden prefix visible to students in Active Code Exercises via Code Lens
@morozov-av is already working on this.
Since Jan 20, 2026.
Assessment
This issue has not been assessed yet.
Description
Please check the current issues Many bug reports are duplicates, this just creates more work for us. Searching the issues first may give you your answer or a workaround! If not adding new information to an existing report is much more helpful than a new report.
What Course are you in
Knowing the course will help us a lot
idahostateuniversity_httlacs_spring26
What Page were you on
N/A
What is your username
norkish
Describe the bug
A clear and concise description of what what you were trying to accomplish and what went wrong. Vague statements like X does not work are not helpful. Imagine if one of your students sent you an email that said, "My program doesn't work, whats wrong with it?" Could you help them with only that to go on?
A student showed me that if they use CodeLens on the Active Code exercises, they are able to see the Hidden Prefix code that I develop for the exercise. Is this a bug or a feature? In any case, I'd like the hidden prefix to remain hidden.
I don't see a way with the new Assignment Builder to deactivate CodeLens. Temporary workarounds could include using the old assignment builder to add the directive or to explicitly include assert statements in my suffix to ensure students don't inappropriately use information stored in the Hidden Prefix, but ideally there would be a way to prevent them from seeing the prefix.
Traceback
If you got here through the Bug Report page and there was a stack trace, please paste it here
Javascript Errors
Many many errors can be quickly diagnosed from the Javascript Console error log. On Chrome this is View --> Developer --> Javascript Console, on Safari ⌥⌘i or Develop --> Show Web Inspector on Firefox Tools --> Web Developer --> Toggle Tools
- Dominant language
- HTML
- Stars
- 135
- Forks
- 197
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from RunestoneInteractive/thinkcspy
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
RunestoneInteractive/thinkcspy#281 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
RunestoneInteractive/thinkcspy#279 · 4 comments ·
-
bug help wanted
Difficulty 3/5 1-2 days Newbie friendliness 35/100
RunestoneInteractive/thinkcspy#278 · 6 comments ·
-
The "Expected" and "Actual" labels on autograded assertions for ActiveCode exercises are backwards Open
Difficulty 3/5 1-2 days Newbie friendliness 35/100
RunestoneInteractive/thinkcspy#276 · 2 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100