15 Commits (90f2b5157af27c6ea365f456df5422ff2bceee02)

Author	SHA1	Message	Date
Henriette Dinger	bd7f4e4814	Update copyright notice	5 years ago
Oliver Günther	29657fbaf1	[30839] Avoid leaking subject in cached WP links ... https://community.openproject.com/wp/30839	5 years ago
Henriette Dinger	086a80edb4	Fix references to revisions and adapt tests	5 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	7cf11bb689	Update copyright notice	8 years ago
Alex Coles	294b0ded6d	Update expected HTML in RevisionRepresenter spec ... Signed-off-by: Alex Coles <alex@alexbcoles.com>	9 years ago
Jan Sandbrink	6e9ed008fb	Enforce passing of current_user into representers ... Thereby permission checks will no longer silently fail if no user was passed. This uncovered a lot of places where we actually expected a user to be passed, when it wasn't. This was especially true for collections. The basic idea is, that virtually all representers could change their behaviour based on the current user. Representers where this is not the case (e.g. Digest), can still explicitly opt-out.	9 years ago
Jens Ulferts	73b53ba9d8	adapt specs to message_chain	9 years ago
Oliver Günther	974f5566e8	Extend revision representer with identifier and revision link ... This commit extends the revision endpoint with a link to the (non-api) revision view as well as the formatted identifier from the Changeset model.	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
Oliver Günther	aa74e9c382	Added specs for revision endpoint	9 years ago