Closed camsom closed 8 years ago
Otherwise LGTM I think this is the most flexible approach. Only immediate downside is the extra code to check for IndexErrors and such -- maybe that could be streamlined by some wrapper if we continue this approach?
@mparent61 updated this to include the next
calls from the most recent djes updates
Much cleaner with next(). As I think you mentioned in the djes update, will the next() call make repeated ES backend queries on subsequent calls against the same query? Or will caching ensure ES is only hit once?
@mparent is this good to go?
:+1:
blessings
@mparent61
This will be imported into the respective reading_lists to add the appropriate query.