[GH-ISSUE #57] Naming conventions for filter views. #128

Open
opened 2026-04-02 22:00:33 -06:00 by gitea-mirror · 0 comments
Owner

Originally created by @emig on GitHub (Jul 9, 2015).
Original GitHub issue: https://github.com/jo/couchdb-best-practices/issues/57

I propose a prefix out in followed by the property.
examples:

filter that filters out design documents: out-design-doc (note we use singular, since the function works on a single item per call)
filter that filters in documents with createdOn property after a passed date: in-createdon-after

in - out allows to prevent using the negative form and is the form used with the verb filter

I don't think we should encode the query params if used, since that would create a strong bound btw the name and the params.

filter combinations

We can combine filter names with generic logic conjunctors: or , and

Originally created by @emig on GitHub (Jul 9, 2015). Original GitHub issue: https://github.com/jo/couchdb-best-practices/issues/57 I propose a prefix `out` `in` followed by the property. examples: filter that filters out design documents: `out-design-doc` (note we use singular, since the function works on a single item per call) filter that filters in documents with createdOn property after a passed date: `in-createdon-after` in - out allows to prevent using the negative form and is the form used with the verb `filter` I don't think we should encode the query params if used, since that would create a strong bound btw the name and the params. ## filter combinations We can combine filter names with generic logic conjunctors: `or` , `and`
gitea-mirror added the
question
label 2026-04-02 22:00:33 -06:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/couchdb-best-practices#128
No description provided.