282 Commits (d80d8b1ecc1e37a6c0693e67063924c3df00175c)

Author	SHA1	Message	Date
Jens Ulferts	f55c9cb6f2	include various representation links into the wp collection rep	8 years ago
Markus Kahl	f5a57e3f42	list custom field normalisation and multi select	8 years ago
Oliver Günther	d862a0e692	Stub ancestor data in representer spec	8 years ago
Jens Ulferts	c4bef2247d	adding filter instance schemas	8 years ago
Oliver Günther	c05a54b40d	Add ancestors information through separate grouped SQL	8 years ago
Jens Ulferts	a022169f23	refactor for linting	8 years ago
Jens Ulferts	74770c6a63	adding query schema - global query	8 years ago
Jens Ulferts	6fe494d8ce	add schema link to wp representer	8 years ago
Jens Ulferts	7312959fa2	refactor embedding schemas in work package representer	8 years ago
Jens Ulferts	8eab60380e	embed schemas in work package list	8 years ago
Jens Ulferts	310c5513c1	linting	8 years ago
Oliver Günther	7cf11bb689	Update copyright notice	8 years ago
Jens Ulferts	455955fc32	use equal method of embedded work package	8 years ago
Oliver Günther	ff8c85c478	[24258] Reuse existing schema after updating work package ... When a work package is updated after a successful PATCH, its schema is being reset to the linked value (and thus, `$loaded == false`). Since this controls type attribute visibility, this always leads to a small period of time where the schema is being retrieved from cache and causes a visible reloading of an attribute section. Here, again, the correct fix is to AVOID loading schemas as links, but rather as a separate state where the referenced schema will always reside unless the switch was made to a new type.	8 years ago
Oliver Günther	3813fbcd36	[24210] Respect `feeds_enabled` setting for atom export link	8 years ago
Oliver Günther	a9f2c55564	[23272] Show linked revisions from other projects if visible ... Revisions in other projects were not shown if the project containing the linked work package did not have a repository itself. https://community.openproject.com/work_packages/23272	8 years ago
Oliver Günther	7d570595fa	[23697] Remove project-specific version from representer (#4720) ... Grouping versions are performed on their names, not on the project-specific name (e.g., `parent - version` in a subproject where this version is shared with). This causes the group name and row value to differ and cause an error. This commit changes the behavior as before. Grouping instead should be made on a unique identifier (valueLink for non-scalar values) and the grouping should generate a project-specific output so that versions can add the above project-specific name.	8 years ago
Jens Ulferts	b3a21283c7	replace the rendering of a hash by a specific WorkPackageSumRepresenter ... That way, the sums follow the general implementation schema and plugins are able to customize displaying the sums.	8 years ago
Oliver Günther	550763ae46	Do not 'inherit' priority from children ... This removes updating of priority values from children to parent work packages.	8 years ago
Oliver Günther	e975809416	Extend WorkPackageCollectionRepresenter with project ... When in project context, createWorkPackage(Immediate) links should not be generated with a global permission.	8 years ago
Jens Ulferts	d18b028599	use assignable_custom_field_values for version as well	9 years ago
Jens Ulferts	5948249c77	no longer show available values for a typed schema ... Before, the available values where always embedded into every schema. Because a deep copy is performed in the front end, this would downgrade the performance of the wp list in cases where a schema has a list cf with a lot of available values	9 years ago
Markus Kahl	bc4902d50f	links for work package export as PDF/Atom (#4581)	9 years ago
Oliver Günther	8a4074fd3f	Stub users in specs since IDs are now required	9 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
Oliver Günther	6204762234	Add the current locale to the schema cache key (#4526)	9 years ago
ulferts	49a09ff109	fix payload object to not show percentageDone when calculated (#4512)	9 years ago
ulferts	2c47657de7	unified date field for milestone work packages (#4437) ... Work packages having a type that is a milestone receive a 'date' attribute in their API resource. Other work packages still have the 'startDate'/'dueDate' attributes. The schema behaves analogous so that such a change is visible to a client. In the cient we can now remove some of the custom behaviour for the date field. The code removal is limited to the new inplace edit implementation as the old implementation can hopefully be removed fully in the near future.	9 years ago
Oliver Günther	14c858a6c3	Remove required state of description	9 years ago
ulferts	4e6d880906	Fix/representer cache key (#4385) ... Moves the calculation for whether the WP schema representer has to be rerendered to the representer itself in the form of the cache_key method. This reduces coupling as the cache_key calculation is based on information the representer already has and the controller now no longer needs to know that information. It additionally uses the same calculation for the E-Tag to reduce duplication. In order to allow plugins to add to that cache_key, the acts_as_op_engine module is extended.	9 years ago
Markus Kahl	50e40f324a	wp form config polish (#4364) ... * allow hiding fields with defaults; consider name_source * sort types by name; move projects config to bottom * updated translations (default => active) * no extra visibility behaviour for new WPs * allow hiding even type; always show details header though otherwise the 'show all attributes' button may vanish * updated specs to include new info	9 years ago
Oliver Günther	29d69a3fc5	Introduce header and Rails caching for schemas ... This commit introduces cached project-scoped work packages schema. Their caches are expired on a key based on - the Project ID - the Type ID - the allowed custom fields for the given project This commit only caches schema, not form endpoints.	9 years ago
Markus Kahl	db29aead44	updated specs to work with new behaviour	9 years ago
Oliver Günther	1d3d58d342	Remove private annotation for descendents of FormRepresenter	9 years ago
Jens Ulferts	ff3d42fa33	add a project independent endpoint to create work packages ... Includes the auxillary end points: * form * schema * available_projects	9 years ago
Jens Ulferts	77d348753d	move CreateFormResource to CreateProjectFormResource	9 years ago
Jens Ulferts	f40d84cc02	move contracts from lib/api to app/contracts	9 years ago
Jens Ulferts	5a977c5594	add resource for querying the list of allowed projects	9 years ago
Jens Ulferts	34b26a4ff4	add service specific for adding notes to a work package	9 years ago
Jens Ulferts	143400629c	use variable in shared context	9 years ago
Jens Ulferts	da7b1d1c40	define project changing behavior in wp contract	9 years ago
Jens Ulferts	dad1596c1f	add specs for other linked attributes on wp payload resource	9 years ago
Jens Ulferts	94cd7f1255	add project to payload representer	9 years ago
Jens Ulferts	0123e70316	adapt specs to altered implementation	9 years ago
Jens Ulferts	09e5815a74	add sumsSchema to api	9 years ago
Jens Ulferts	55814ecd40	reenable context menu	9 years ago
Jens Ulferts	32b3b9ab9b	replace html path in api representer ... The html path is no longer required as we now have a proper api endpoint a client can call	9 years ago
Jens Ulferts	fc49e2a7b7	use linked parent resource instead of parentId ... The parentId field should be removed. But we shouldn't do it in a minor version.	9 years ago
Jens Ulferts	9668e7e99e	fix addChild path in work package resource	9 years ago
Jens Ulferts	966d749e45	add parentId field to schema ... This is somewhat debateable. Having a parentId field is wrong in itself. It should be a linked resource. But as the field is also present in the resource, it also needs to be part of the schema for consistency sake.	9 years ago