Changes between Initial Version and Version 1 of Ticket #22124


Ignore:
Timestamp:
02/22/2014 10:17:41 AM (19 months ago)
Author:
bmispelon
Comment:

I'll mark this ticket as accepted on the basis that there's probably some improvements to be made on this fairly new part of our documentation.

Are there other points beside the one you mentionned in the ticket that you think could be improved?

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #22124

    • Property Patch needs improvement unset
    • Property Needs tests unset
    • Property Version changed from 1.6 to master
    • Property Needs documentation unset
    • Property Type changed from Uncategorized to Cleanup/optimization
    • Property Triage Stage changed from Unreviewed to Accepted
  • Ticket #22124 – Description

    initial v1  
    1 Custom Lookups look great, however, I find the documentation terse. Example: no explanation what
    2  lhs, lhs_params = self.process_lhs(qn, connection)
     1Custom Lookups look great, however, I find the documentation terse. Example: no explanation what
     2{{{#!python
     3lhs, lhs_params = self.process_lhs(qn, connection)
     4}}}
    35is exactly.
    46
    5 The explanation: "lhs
    6 The lhs (left-hand side) of a lookup tells us what we are comparing the rhs to. It is an object which implements the query expression API. This is likely to be a field, an aggregate or a subclass of Transform.
    7 does not explain" does not explain what lhs_params might be. Also a search on "process_lhs" on complete Django website only points to this page (no other pages).
     7The explanation:
     8
     9> lhs
     10> The lhs (left-hand side) of a lookup tells us what we are comparing the rhs to. It is an object which implements the query expression API. This is likely to be a field, an aggregate or a subclass of Transform.
     11
     12does not explain what `lhs_params` might be. Also a search on `process_lhs` on complete Django website only points to this page (no other pages).
Back to Top