Jan Sandbrink f9d8bc6614 Introduce SubclassResponsibility error ...

This error is intended for cases when a method is
intentionally not implemented, because the module/class defining
it expects a subclass (or class including the module) to implement
the method.

This is intended to distinguish it from other cases, such as:
* feature not implemented yet
* edge case of a method call not yet supported

Notably it avoids the misuse of the Ruby-defined NotImplementedError,
which is only intended for much more specific scenarios:

> Raised when a feature is not implemented on the current platform. For example, methods depending on the fsync or fork system calls may raise this exception [...]

Also see https://docs.ruby-lang.org/en/master/NotImplementedError.html

2026-03-27 08:14:56 +01:00

..

hierarchy

Introduce SubclassResponsibility error

2026-03-27 08:14:56 +01:00

custom_field_projects_controller.rb

Fix custom field projects

2026-02-09 15:08:20 +01:00