6 Commits (a649a0c4e3da949d9a613ddedc9ec620b59ca4cd)

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	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	7cf11bb689	Update copyright notice	8 years ago
Markus Kahl	5bec815324	updated 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	8 years ago
Oliver Günther	41e7031f27	Additional corrections ... * Use 'has no link' for missing revisions link spec * Avoid duplicate get request	9 years ago
Oliver Günther	2a31d9cabd	Corrections from review ... * Return Unauthorized according to specification * Added revisions by work package specs for users without wp permission (404) and with wp, but without changeset permission (403) * Corrected paths * Use existing link shared examples * Add revision link representer specs * Test for missing author link in revison representer	9 years ago
Oliver Günther	ec3a5b9da7	Browse revisions by work package with linked collection	9 years ago
Jan Sandbrink	8a0a60445b	update root representer ... - add it to the documentation - only provide links to resources that can be directly used (i.e. without templating) - provide useful general instance information	9 years ago
Alex Coles	3276c4ebb5	Add/update Copyright headers in specs ... Signed-off-by: Alex Coles <alex@alexbcoles.com>	10 years ago
Jan Sandbrink	f54781dc6b	use path helper in integration tests ... this should help in avoiding broken links with passing integration tests... after all, the only links a client should use are the ones provided by us, so they should work as intended...	10 years ago
Alex Coles	5afc11f19e	Fix syntax (w/Rubocop) in specs ... Signed-off-by: Alex Coles <alex@alexbcoles.com>	10 years ago
Jens Ulferts	3dfdae1cf9	moving request specs to proper directory, really	10 years ago
Jens Ulferts	6d162fd6ed	moves routing specs to proper directory	10 years ago
Alex Coles	008bca7422	Add skeleton API v3 root endpoint ... Signed-off-by: Alex Coles <alex@alexbcoles.com>	10 years ago