20 Commits (f8aca6a2a85d5b087280d691698f262698c68996)

Author	SHA1	Message	Date
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
Jan Sandbrink	dcd2a3b03c	rework error instantiation ... - multiple errors are no longer a special case of specific errors - there is a separate error class to represent multiple API errors - convert ActiveRecord errors to API errors in a single place, ideally work with API errors from there on	9 years ago
Alex Coles	57618b25ec	Replace dynamic finder usages with #find_by, etc. ... This patch replaces all dynamic finders, for the sake of consistency, although only some methods are deprecated. See: https://github.com/rails/activerecord-deprecated_finders#active-record-deprecated-finders * Revert some `User#find_by_login` usages in cuke steps accidentally removed in 74228b59. User Story # 20325 Signed-off-by: Alex Coles <alex@alexbcoles.com>	10 years ago
Jan Sandbrink	dea02be5b8	return proper error when adding invalid relations ... Error could probably be improved, but so can the whole relations endpoint... I'd consider this a strong case of broken window syndrome and will fix it as soon as we fix the whole relations endpoint...	10 years ago
Jan Sandbrink	a250ede762	return proper error when adding invalid relations ... Error could probably be improved, but so can the whole relations endpoint... I'd consider this a strong case of broken window syndrome and will fix it as soon as we fix the whole relations endpoint...	10 years ago
Jan Sandbrink	b1ba33c75b	specify classes explicitly rather than implicitly ... This is a new try for the APIv3 classes, we either: - FULLY qualify a class and let the autoloader do the rest - don't qualify at all, but require the class explicitly Thus we do not (yet) completely give up on the rails autoloader, but we circumvent a fair amount of its magic (and problems). The hope is to eliminate the following problems in development mode: - NameErrors because the autoloader infers the wrong prefix - "object is not missing constant" errors occuring more rarely Let's see how that turns out to work...	10 years ago
Jan Sandbrink	f0863f9d53	allow to patch existing API endpoints	10 years ago
Jan Sandbrink	a72ea0d5af	more consequently use route_param ... this seems to be the GRAPE-iest way possible	10 years ago
Hagen Schink	db8bfba3af	Remove usage of reform from API V3	10 years ago
Alex Coles	45297523c2	Fix syntax (w/Rubocop) in lib code ... Signed-off-by: Alex Coles <alex@alexbcoles.com>	10 years ago
Marek Takac	99bda3c64a	Set relations delete endpoint to use correct id	10 years ago
Marek Takac	ff6714bfaf	Changed delete to destroy when removing relation	10 years ago
Marek Takac	3d6948662e	Changed the way relation is saved in relations API	10 years ago
Alex Coles	a89522e2df	Remove calls to #to_json in RelationsAPI ... Rely instead on custom Formatter: see 0bf314f1 Signed-off-by: Alex Coles <alex@alexbcoles.com>	10 years ago
Richard	e50db0208a	Use full error messages for relations validation.	10 years ago
Richard	62c9f793bb	Rename relations api namespace from id to relation_id.	10 years ago
Richard	b5f1346a4f	Track down super irritating related to/by bug	10 years ago
Marek Takac	68a526844d	Added authorization to creating and deleting relations	10 years ago
Marek Takac	651d524194	Added endpoint for deleting relationships	10 years ago
Marek Takac	613b71df0f	Added endpoint for creating relations	10 years ago