15 Commits (19282beaab6ee258eddb373f0b081470b8c94b08)

Author	SHA1	Message	Date
Oliver Günther	059770f533	FactoryGirl => FactoryBot ... Removes the deprecation	7 years ago
Oliver Günther	6ef4211e77	Bump copyright to 2018 (#6171) ... [ci skip]	7 years ago
Jens Ulferts	b97d79af2e	additional specs	7 years ago
ulferts	83e605e63c	allow setting parent that has relation via new siblings (#6114) ... [ci skip]	7 years ago
Oliver Günther	3facc5851d	[26829] Patch reform-rails to use activerecord i18n_scope (#6105) ... The validator passed to AM::Error does not use the `i18n_scope` we define on either Reform::Form or the model, but is delegated from the included AM::Translations module. This in turn causes I18n to lookup the scope `:activemodel`, failing the localization. https://github.com/trailblazer/reform-rails/issues/56 https://github.com/trailblazer/reform-rails/pull/35 [ci skip]	7 years ago
ulferts	6b9e7066fd	streamline relation in hierarchy error message (#6056) ... [ci skip]	7 years ago
Jens Ulferts	690e0ffc60	wp create/update/destroy via services	7 years ago
Jens Ulferts	6fdd122534	merge wp tree and relations into typed_dag ... Instead of having the tree/hierarchy information for work packages and the relations between the work packages separated into two tables all the information is now stored in the relations table. To support this, the typed_dag plugin is used. Notable changes: * relations_to and relations_from are swapped. relations_to has all relations that point to another work package (from_id = work_package.id) and relations_from contains all relations that lead to the work package from another one (to_id = work_package.id). This change is merely in the code. The db information is left untouched. * For follows/precedes to_id and from_id are swapped in the db. Because of that, "follows" is now the canonical name instead of "precedes". This is done so that hierarchy relations and follows relations point into the same direction which allows to easily detect cyclic relationships that would lead to infinit scheduling. * the columns `root_id`, `lft`, `rgt` do no longer exist in the wp table. * the column `relation_type` does no longer exist in the relations table. * For every type of relation a column (integer) does now exist in the relations table (e.g. hierarchy, block, follow) * Separate associations exist for every type of relation into two directions. E.g. Work packages following the current one can be accessed via `work_package.precedes`	7 years ago
ulferts	0c0b16508b	Fix/bump representable (#5465) ... * bump reform and roar -> bumps representer * adapt to changed validation interface * disable initializer patch for now * adapt to changed representable attr interface * can no longer have private methods inside a representer * private no longer possible for representer * bump reform * wip - restyle validation * remove commented out patch * apply injection as prescribed * reactivate reform error symbols patch * remove patch to Hash superfluous wit ruby 2.3 * remove outdated human_attribute_name patch * whitespace fixes * adapt filter name after removal of human_attribute_name patch * adapt filter specs to no longer rely on human_attribute_name patch * fix version filter name * remove reliance on no longer existing human_attribute_name patch * use correct key in journal formatter * remove private from representer * adapt to altered setter interface * reenable i18n for error messages in contracts * no private methods in representer * defined model for contracts * fix validaton * instantiate correct Object * define model for contract * circumvent now existing render method on reform * replace deprecated constant * patch correct reform class - not the module - via prepend * refactor too complex method * replace deprations * remove remnants of parentId * prevent error symbols from existing twice * adapt user representer to altered setter interface * adapt watcher representer to altered setter interface * remove now unnessary patch * adapt setter to altered interface * adapt spec * fix custom field setters * remove parentId from wp representer As the parent is a wp resource, clients should use the parent link instead * adapt spec to changed valid? interface * remove parentId from wp schema * replace references of parentId in frontend * remove TODO [ci skip]	8 years ago
ulferts	21571ac3a2	Fix/add child rescheduling (#5499) ... A work package that is to be added as a child needs to be rescheduled to not validate any constraints posed by relations the parent work package might have [ci skip]	8 years ago
Oliver Günther	7cf11bb689	Update copyright notice	8 years ago
Oliver Günther	287613d684	Rubocop	9 years ago
Oliver Günther	1c9ad6d4a2	Extend UpdateContract to allowe parent_id changes	9 years ago
Jens Ulferts	de33104d11	add a project independent endpoint for work package creation	9 years ago
Jens Ulferts	f40d84cc02	move contracts from lib/api to app/contracts	9 years ago