Red Hat Bugzilla – Bug 1010757
Topic Filter should use the topic endpoint and not contentspecnode
Last modified: 2014-07-13 17:10:55 EDT
The Topic Filter in the DocBuilder currently works by doing a query on the contentspecnode endpoint, however if new topic types are added then this is going to fail. It would make more sense to do a query on the topic endpoint and expand the "contentSpecs" collection. This would also allow for all the data to be pulled down in one request instead of a request per topic id.
Can you rephrase this into a user story?
Fixed in the devel branch of DocBuilder2. The query has also been compacted down to a single query as well instead of a query per topic id.
Verified that queries now used the topic endpoint and expand the content specs.
Also confirmed that new node types like info topics can be used to filter the list.