This represents the timelines plugin that was merged with the
OpenProject core and which had its history squashed. The timelines
plugin development was sponsored by;
Deutsche Telekom AG <opensource@telekom.de>
Requirements engineering and management were provided by;
Deutsche Telekom AG <opensource@telekom.de>
Finn GmbH <info@finn.de>
During the timelines development, the following authors have contributed
commits;
Martin Czuchra <m.czuchra@finn.de>
Nils Kenneweg <n.kenneweg@finn.de>
Romano Licker <r.licker@finn.de>
Gregor Schmidt <g.schmidt@finn.de>
Jens Ulferts <j.ulferts@finn.de>
Johannes Wollert <j.wollert@finn.de>
Quality Assurance was provided by;
Erdem Kabadayi <e.kabadayi@telekom.de>
Julia Pape <j.pape@finn.de>
Christian Rijke <c.rijke@finn.de>
Thomas Vogel <th.vogel@external.telekom.de>
When joining issues and projects both tables come with their set of nested_set attributes. The attributes are named equally in both tables. This leads to ambiguous references when calling e.g. Issue.find(1).visible.descendants.
This fix scopes the nested_set to reference the left attribute fully qualified.
Adds additional methods that can be applied should the need arise.
We should reevaluate why nested set is vendored as the problem would not have arisen when using the gem.
The provided proc is dynamically assigned to an anonymous class which inherits from JournalFormatter::Proc. This class, a subclass of JournalFormatter::Attribute, is instantiated along with the other formatters once a field registered on the formatter needs to be formatted. The proc is then called within the value formatting.
Some plugin, e.g. acts_as_attachable and acts_as_customizable, dynamically add associations to a model following a schema, e.g attachments_[n], where n is increased over time.
To better allow for customization, formatting journal entries is moved
to separate classes. One can register for each field of a journaled
object the same way like before (e.g. register_on_journal_formatter
(:plaintext, 'subject')). The difference is purely inside the
JournalFormatter. It determines the formatter required for the given
field and class, instantiates it and calls the render method on the
instance.
JournalFormatter::Base subclasses are provided to handle the most common
types of formatting (e.g. plaintext and decimal).
The OpenProject formatters are removed altogether from
acts_as_journalized and are moved into the OpenProject /lib directory.
The helper_issues_show_detail_after_setting hook is removed. It should
no longer be needed.
* Adding special URL endpoint to get all visible projects at once (w/o paging -
as in /projects/index.json)
* Adding openProject JS object to carry useful information and helper methods
for JS land
* Adding helper method to User to get the number of visible projects w/o loading
all of them
* Reducing dependency to DOM structure of select2 - using API access instead
* Close menu when select2 list is closed
also include that module wherever ActionView::Helpers::TagHelper is included, since it's very likely that they are used together
we should probably remove #h completely if possible? is it? do we? don't know yet
Alex Coles
Hagen Schink
Martin Czuchra
Philipp Tessenow
Jens Ulferts
Eric Davis
Gregor Schmidt
Martin Linkhorst
Martin Linkhorst
Jean-Philippe Lang