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

Come up with a better grader inheritance concept #210

Open
alexstaeding opened this issue Feb 12, 2023 · 0 comments
Open

Come up with a better grader inheritance concept #210

alexstaeding opened this issue Feb 12, 2023 · 0 comments

Comments

@alexstaeding
Copy link
Member

The primary use case for multiple graders in a project is the split between public/private graders. Because inherited graders are combined with duplicate resolution always favoring the "base" grader (i.e. private grader), combining existing test classes or rubrics in the public grader with ones in the private grader is cumbersome.

The current options are:

  1. Copy the entire class into the base grader with modifications. Rely on duplicate file exclusion to favor the class in the private grader.
  2. Extract the the logic of the class and reference it. Similar to 1. but the duplicate code is just method calls to the actual logic which is extracted.

Find a better solution to this problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant