/search

[venkatramanm]

can we pass an additional intent attribute called "require", the value for this attribute would one of these enums:

items, categories , providers.

this will enable

1. bytes transferred as needed for bap ui.
2. drill down kind of ui.

while this is possible using intent tags but that could cause divergence between networks/directories.

@ravi-prakash-v @pramodkvarma

[ravi-prakash-v]

Hi @venkatramanm could you please explain the background context, highlight the problem, and then outline the proposed solution?

[venkatramanm]

Often times for user experience, a bap may want to show either categories or providers at first level and drill down to items at next level.

default /on_search payload can be often quite verbose e.g if provider_id or catagory _id is not passed. listing all items could be excessive.

truncating payload may not be optimimal solution.

in order to enable such usecases efficiently, we could take input from bap and return only providers or categories .

this way another search may be fired to get items for a more granular criteria.

that's the usecase being referred here.

[venkatramanm]

kind of like a limited version of graphql

[venkatramanm]

#267 was related issue