11 Commits (cbcc4627f5c755a3d02526251332edb7ee904725)

Author	SHA1	Message	Date
Henriette Dinger	bd7f4e4814	Update copyright notice	5 years ago
ulferts	e1027189bb	eager load associated work packages of relations (#6315) ... [ci skip]	7 years ago
Jens Ulferts	26320fe614	eager load for relations	7 years ago
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	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
Oliver Günther	507c2d26ea	Remove fromType, toType	8 years ago
Oliver Günther	f3df45cef4	Extend backend relations API with WP type information ... This saves the doubled frontend request just to find out which types work packages of a specific relation have. Since the connection between work package types and relation types are very close, we should always send them.	8 years ago
Oliver Günther	7cf11bb689	Update copyright notice	8 years ago
Markus Kahl	7f6d74a88e	basic crud	8 years ago
Markus Kahl	994e0db591	add rel desc; brought representer up to spec	8 years ago
Jens Ulferts	8136a3a26f	implements a relations collection ... * Replaced the non standard array on the work package resource with the collection * Adds an endpoint for querying for the resource * adds a link pointing to the endpoint to the work package resource Does not add an end point for querying for a single relation. There is a link in the relation resource but it points into the void. Does also not improve the weird behaviour of changing the relation type based on the work package passed into the representer	9 years ago