When searching using a child class of Object (in the mapping module) the defined fields should be pre-populated using the /values endpoint
Bug #812246 reported by
Nicholas Tollervey
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fom |
Fix Committed
|
Undecided
|
Nicholas Tollervey |
Bug Description
It appears that if you define a class that subclasses Object and call the filter("query") method the resulting list contains instances whose attributes have not been pre-populated using the /values endpoint. In the interests of reducing latency we should attempt to pre-populate the result-set.
Related branches
lp:~ntoll/fom/instance-pre-populate-search-812246
- Jamu Kakar: Approve
- Diff: 0 lines
Changed in fom: | |
assignee: | nobody → Nicholas Tollervey (ntoll) |
status: | New → Confirmed |
status: | Confirmed → In Progress |
Changed in fom: | |
status: | In Progress → Fix Committed |
To post a comment you must log in.