Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable maintenance-mode exercises that aren’t visible in ToC #1124

Closed
jsorva opened this issue Jan 3, 2023 · 1 comment · Fixed by #1183
Closed

Enable maintenance-mode exercises that aren’t visible in ToC #1124

jsorva opened this issue Jan 3, 2023 · 1 comment · Fixed by #1183
Assignees
Labels
area: user interface User interface issues that are not specifically about navigation or user experience (UX) effort: hours Estimated to take less than one day, from the creation of a new branch to the merging experience: beginner required knowledge estimate requester: CS The issue is raised internally by a CS teacher type: feature New feature or change to a feature

Comments

@jsorva
Copy link

jsorva commented Jan 3, 2023

AFAIK, there’s currently no way to put an exercise in maintenance mode while simultaneously hiding it from the ToC. However, that’s precisely what I’d normally like to do when I put an exercise in maintenance mode, and I know of other teachers who’d like to do the same.

(Context: My exercises aren’t normally listed in the ToC — but they very visibly appear there if they’re put into maintenance mode, which is counterproductive.)

Suggestion: either hide all maintenance-mode exercises from the ToC or add another option to the list of exercise statuses.

@jsorva
Copy link
Author

jsorva commented Jan 29, 2023

A closely related old issue: #438

@PasiSa PasiSa added this to the Summer 2023 milestone May 18, 2023
@markkuriekkinen markkuriekkinen added type: feature New feature or change to a feature area: user interface User interface issues that are not specifically about navigation or user experience (UX) effort: days Estimated to take less than one week, from the creation of a new branch to the merging experience: beginner required knowledge estimate requester: CS The issue is raised internally by a CS teacher labels May 23, 2023
ihalaij1 added a commit to ihalaij1/a-plus that referenced this issue May 29, 2023
ihalaij1 added a commit to ihalaij1/a-plus that referenced this issue May 29, 2023
ihalaij1 added a commit to ihalaij1/a-plus that referenced this issue May 29, 2023
ihalaij1 added a commit to ihalaij1/a-plus that referenced this issue May 29, 2023
ihalaij1 added a commit to ihalaij1/a-plus that referenced this issue May 29, 2023
@ihalaij1 ihalaij1 self-assigned this May 30, 2023
@markkuriekkinen markkuriekkinen moved this from Todo to Under review in A+ sprints May 30, 2023
@markkuriekkinen markkuriekkinen added effort: hours Estimated to take less than one day, from the creation of a new branch to the merging and removed effort: days Estimated to take less than one week, from the creation of a new branch to the merging labels May 30, 2023
ihalaij1 added a commit to ihalaij1/a-plus that referenced this issue May 30, 2023
markkuriekkinen pushed a commit that referenced this issue May 31, 2023
@github-project-automation github-project-automation bot moved this from Under review to Done in A+ sprints May 31, 2023
markkuriekkinen pushed a commit to markkuriekkinen/a-plus that referenced this issue Jun 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: user interface User interface issues that are not specifically about navigation or user experience (UX) effort: hours Estimated to take less than one day, from the creation of a new branch to the merging experience: beginner required knowledge estimate requester: CS The issue is raised internally by a CS teacher type: feature New feature or change to a feature
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

4 participants