Remove subgraph query from algorithm component about market HOT 4 CLOSED

Currently, there is a limitation of 1000 elements in that view(that is dictated by the subgraph query)

What I see on the code is that we're making a query to aquarius to get the algoriths (query endpoint: https://v4.aquarius.oceanprotocol.com/api/aquarius/assets/query). This query is the one returning the 1000 records for the c2d dataset. There's no subgraph query involved in the retrival of the algos.

UPDATE: I found the issue, is not on the subgraph side, it's the aquarius query here. If we increase the size value, c2d energy shows up. Currently there's 1146 records for this dataset.

from market.

@mihaisc I'm looking at the code. The price gets calculated when you select an algo, what do you mean for "we want to calculate the price once the user selects an algorithm" (it's already like that)?

Basically we need to:

• remove subgraph query from component (only use aquarius)
• show the price from aquarius (i'll check again, but it seems already like that)
• show the missing asset

from market.

@mihaisc @AnaLoznianu

I still have some question:

• remove subgraph query from component (only use aquarius)

Is this what's required?

• show the price from aquarius (i'll check again, but it seems already like that)

I see on the code we're showing the price from aquarius. Am I wrong?

• show the missing asset

I can't find the dataset we discussed on the standup. Are we supposed to find it on the algo list?

from market.

@EnzoVezzaro I'm not sure if this is helpful but lemme give some context for this story. Currently, there is a limitation of 1000 elements in that view(that is dictated by the subgraph query). We reached that limit and new algos are no longer shown in that list. If we remove the subgraph query we should be able to bypass that limitation and display more algos.

from market.