Skip to content

Refactor exercise_accessible and is_revealed #1242

Open

Description

@lainets

The exercise_accessible tag should be refactored to work similarly to the is_listed and is_visible tags (or later methods with the new cache changes done in PR #1231). This means saving whether it is accessible to the cache (or saving enough data to the cache to easily compute whether it is accessible) and checking that instead of computing the value in the templatetag file exercise/templatetags/exercise.py. As part of this refactoring, the is_revealed attribute (in CachedPoints) should be taken into account in whether it is accessible, and the is_revealed checks can be removed from the HTML files.

Activity

  1. added
    type: refactoringRefactoring of code without changing features
    effort: daysEstimated to take less than one week, from the creation of a new branch to the merging
    requires: priorityCurrently using this label to flag issues that need EDIT decision ASAP (even if there was priority)
    on Sep 1, 2023
  2. moved this to Todo in A+ sprints on Sep 6, 2023
  3. self-assigned this
    on Oct 16, 2026
  4. moved this from Todo to In progress in A+ sprints on Oct 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

effort: daysEstimated to take less than one week, from the creation of a new branch to the mergingrequires: priorityCurrently using this label to flag issues that need EDIT decision ASAP (even if there was priority)type: refactoringRefactoring of code without changing features

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions