624 Commits (908958780d3de5ee1bd389ef87298749b12ca082)

Author	SHA1	Message	Date
Henriette Dinger	867b273c8a	Set default wp type	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	02ff24b3b2	Add type#updated_on to cache key	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
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	de33104d11	add a project independent endpoint for work package creation	9 years ago
Jens Ulferts	4cd20973e2	improve CreateWorkPackageService to conform with new interface	9 years ago
Jens Ulferts	5a977c5594	add resource for querying the list of allowed projects	9 years ago
Jens Ulferts	c8d1850543	allow setting new custom field values when changing the project	9 years ago
Jens Ulferts	a1d8d483b8	initial request spec for editing project on wp resource	9 years ago
Jens Ulferts	09e5815a74	add sumsSchema to api	9 years ago
Markus Kahl	498447c91b	set required setting to fix specs	9 years ago
Jens Ulferts	b2551f92e2	enable Rack::Deflater ... Rack::Deflater will compress every response served by the Rack stack if the appropriate ACCEPT_ENCODING header is set (e.g. HTML, JSON, ...). Assets would be compressed too if they would be served by the application directly. As the ACCEPT_ENCODING header suggests compressing (e.g. "gzip, deflate") by default on all browsers I looked into, there is nothing to do on the client side of the application. This is also true on the XHR requests.	9 years ago
Jan Sandbrink	85f60d8bbc	Also allow to add attachments to a WP with permission to add WPs ... This is neccessary to allow adding attachments, after creating a new work package. The undesired part is, that it also allows you to add attachments long after creating the WP.	9 years ago
Oliver Günther	acb4431d8a	Implement UserPreferences endpoint ... Provides the implementation to the user preferences endpoint.	9 years ago
Mohamed Wael Khobalatte	03cce5e25d	Avoid defining same constants in multiple specs	9 years ago
Stefan Botzenhart	1c01b5801e	Use login_as helper method throughout all specs	9 years ago
Jens Ulferts	dac4459100	restructure available principals spec for better readability	9 years ago
Jens Ulferts	3e12f109b6	restructuring available assignees/responsibles api spec ... * They no longer mock as request specs should refrain from mocking * They are now merged into one file as the behaviour is very similar	9 years ago
Jan Sandbrink	e9031a38b1	Reintroduce clear statements that were still neccessary	9 years ago
Markus Kahl	4eda276ecb	always clear delivieries so one does not have to worry about it	9 years ago
Oliver Günther	3ca36e1e1d	Parallel sending of comment and fields in WP split view ... Parallel submitting of comments alongside WP edits wasn't possible natively due to the increased lock_version in work packages, caused by `touch`ing and explicitly saving the work package in the process of adding a journal. This commit works around this issue by updating the timestamp columns directly, bypassing optimistic locking in the work package table. This allows comments to be submitted transparently with other fields to the user, while actually, we send it in two subsequent steps.	9 years ago
Oliver Günther	0aed8bb310	Test for comment input	9 years ago
Alex Coles	27d363df78	Use #be_html_eql matcher in APIv3 Render spec ... Signed-off-by: Alex Coles <alex@alexbcoles.com>	9 years ago
Jan Sandbrink	ab9d502009	Allow to delete work packages via APIv3	9 years ago
Jan Sandbrink	5de0f15898	Correctly link activities ... - they might not be embedded - create an endpoint for activities - document it properly - adapt angular client	9 years ago
Jan Sandbrink	5d473e9a9c	fix HTTP response of DELETE attachment ... this was wrongfully HTTP 202 (Accepted), which would only be valid if we did the deletion in a delayed/deferred way. For now using HTTP 204 (No Content), since we have no response body.	9 years ago
Jan Sandbrink	32e638449b	hide lockVersion from work package columns	9 years ago
Jan Sandbrink	637fadf602	add endpoint to list work package columns in a project	9 years ago
Jan Sandbrink	aa5155c8b7	fix specs ... - also extend WP schema specs	9 years ago
Jan Sandbrink	0a73e6bac4	convert attribute names in queries API ... This should make the API more consistent again, accepting and producing the same attribute names on all endpoints	9 years ago
Jan Sandbrink	602d488c66	fix reference to value links	9 years ago
Jan Sandbrink	73716ed40a	improve rubocop-perceived styling	9 years ago
Jan Sandbrink	c6336fd5a1	add some integrative specs for sum/group/sort/filter	9 years ago
Jan Sandbrink	e6c7a0ce9f	add global WP list endpoint	9 years ago
Jan Sandbrink	bc36704611	allow to get queries via APIv3 ... - one of those missing endpoints - adapted resource spec to be closer to other resource specs - specified error behaviour (missing permissions) -> change: not being allowed to see a query results in 404	9 years ago
Jens Ulferts	3aa8a144d6	adapt specs to send mails on self action	9 years ago
Jens Ulferts	c471080e08	set locale before API v3 request ... The mechanism was extracted from the rails stack where the locale is taken based on (in that order): * The user's preferences * The accept_language header * The system settings Only languages, that are enabled by the instance are valid. If one is selected (e.g user preference), that is not enabled by the instance, a fallback is taken.	9 years ago
Jan Sandbrink	86aa756df2	actually implement endpoint for WPs by projects	9 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
Oliver Günther	aa74e9c382	Added specs for revision endpoint	9 years ago
Jan Sandbrink	3d49831bfd	extract activities by WP into own endpoint	9 years ago
Jan Sandbrink	563cb3c5c7	migrate APIv3 to aggregated journals ... - turns out agrgegated journals needed more features - turns out specs were incomplete and bogus	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
Jan Sandbrink	17940bf02c	change validation of WP children ... - do not add error on a symbol called :#123 (123 is the childrens ID) - this is against the semantics of ActiveRecord::Errors - creating symbols in a loop used to be a bad idea (might be better today) - it breaks error messages in the APIv3 (which is due to APIv3 working beyond the borders of AR errors, not the best of ideas...) - use :base instead, the place for unlocatable errors - include the fact that #123 refers to a child element in the error message Basically I feel that this makes the children validation cleaner and better. But somehow I fear, that there is some code out there that depends on the fact that error keys like :#123 existed...	9 years ago