-
Notifications
You must be signed in to change notification settings - Fork 260
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
Redesign to support other scoring methods #2525
Labels
Comments
Some comments/questions for this:
|
Some thoughts here:
|
Hi! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In the past there have been various requests to support other scoring methods than pass/fail with penalty time, some have been listed in scoring
Before we try to support any of these, we should consider what a common (internal) interface/data structures would look like to generically support these. This would include making a trade-off where the more weird scoring methods we'd support, the broader and less well-defined this interface would become. This ticket is to discuss that interface.
We should then also refactor our code so that all scoring related code is hidden behind implementations of this interface. Currently there is plenty of code scattered around the code base.
The text was updated successfully, but these errors were encountered: