Changes between Version 1 and Version 2 of S3/FieldSelectors

Timestamp:

05/01/14 11:07:17 (11 years ago)

Author:

Dominic König

Comment:

--

S3/FieldSelectors

@@ -139 +139 @@
 {{{#!python
 # Filter expression valid for both project_project and org_office:
-query = S3FieldSelector("(location)$name") == "Example
+query = S3FieldSelector("(location)$name") == "Example"
 }}}
 
 Only when the field selector gets resolved against each resource (e.g. during add_filter), the "(location)" part is translated according to the respective "context" configuration.
 
+It is possible to include the target field in the context expression:
+
+E.g. in this example, if we wanted to filter by location_id, then "(location)" would be a valid field selector for both resources:
+
+{{{#!python
+# Filter expression valid for both project_project and org_office:
+query = S3FieldSelector("(location)") == 43L
+}}}
+
+Context paths can be used for various purposes, e.g.
+
+  - profile pages which show multiple resources all in the "context" of the same primary record, e.g. all offices, projects, etc related to the same location (=primary record)
+  - filter forms across multiple resources (dashboards, not implemented yet)
+  - global filters for all pages (s3db.context)