On Thu, Jan 12, 2012 at 11:13 AM, osimons <[email protected]> wrote:
> Right, so 'tickets' is actually not a list of ticket objects... Chris, > it really makes sense for your code to follow the common Trac practice > of passing actual objects around instead of mutating them into various > structures. It just makes it so much harder for everyone, and makes > code less readable and questions harder to anwser. In everything I > read in your question and code, t should be a trac.ticket.model.Ticket > object - and 'tickets' should be a list of them.... Tracing through the code where ``tickets`` is defined ( http://trac-hacks.org/browser/tracjsganttplugin/0.11/tracjsgantt/tracjsgantt.py#L546 ) I see that it's actually the result of a trac.ticket.query.Query().execute() call, which returns a list of raw dicts: http://trac.edgewall.org/browser/trunk/trac/ticket/query.py#L326 Does a higher-level or more formal API exist in Trac core for fetching tickets from a query? I remember looking for one a while ago and not finding anything. -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.
