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
Creates the following Primerized components:
* `AttributeHelpTextComponent` to render an icon that will invoke the
attribute help text dialog on click.
* `AttributeLabelComponent` to render an attribute label and help text
icon together with the correct spacing.
* `AttributeHelpTexts::ShowDialogComponent` to render the attribute help
text dialog itself.
Also creates accompanying Controller actions, routes and specs.
Updates the copyright to 2021 for all files that have a copyright. Files in our source code without the copyright header still do not receive one automatically. Additionally, backlisted files are also excluded.
Previously the copyright of chiliproject which references redmine stated a copyright of redmine up to and including 2017 which is not true for the code we have in here. Because of that I changed that to 2013
Attribute help text so far could only be added to work packages.
This commit adds support for projects and adds the help texts to
widget headers for status and description modals in the overview tab
as well as extending the attachable mixin to allow uploading images.
Uploaded attachments are to be expected to be visible regardless of permissions,
thus this also adds an option to make attachments visible to all
Uses FactoryBot to keep and maintain specific records in a special transaction that does not get removed after each spec.
They automatically are created whenever first hitting them.
This makes an excellent time saver for items that are commonly used, such as an admin user account
* code prettification
* avoid help text for newly added cf requiring restart
When using the class method statically, the values are determined upon reading the class. By that, a restart is required before newly added custom fields are added to the list and removed custom fields will still be listed
* limit visibility of attribute help texts
[ci skip]
Jan Sandbrink