14 Commits (48591e9bbdc83e7836a8f72f2d3da2b59501e3ef)

Author	SHA1	Message	Date
Jens Ulferts	4c32d17ede	add query form stub - not production ready	8 years ago
Jens Ulferts	c4bef2247d	adding filter instance schemas	8 years ago
Jens Ulferts	473f7ea216	embedding and linking to available columns when embedding query schema	8 years ago
Jens Ulferts	bf59283993	rename query properties	8 years ago
Jens Ulferts	27362f785a	embed filters as objects	8 years ago
Jens Ulferts	58df267bc4	link to sort_bys	8 years ago
Jens Ulferts	9cb9096491	link to group_by	8 years ago
Jens Ulferts	3f2c0e6a3d	link to column names	8 years ago
Jens Ulferts	80c242dd53	embed query results in query representer ... This is only done when the representer is not embedded itself, e.g. when it is part of a collection.	8 years ago
Oliver Günther	7cf11bb689	Update copyright notice	8 years ago
Jens Ulferts	1a597e180b	first step towards generalizing the query and its filters	8 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
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	77f2b2a1cc	align the query representer with APIv3 ... - correctly use datatypes - link to linkable resources (instead of embedding their properties) - add specs	9 years ago