Subgraph helpers for assetSelection list and previous orders

[bogdanfazakas]

Fixes # .

Changes proposed in this PR:

• set price for each asset in AssetSelection from the graph
• get previous orders for compute selceted assets from the graph

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/oceanprotocol/market/8mkDg1Mdm5GPHdYFCuzj3jMhQMYp
✅ Preview: https://market-git-feature-sugraph-util-methods-oceanprotocol.vercel.app

[kremalicious]

awesome, confirmed all prices are in sync in this place now:

Getting this though, but I guess this is actually what we want now when checking for isOrderable?

Bit confusing to users as to what is wrong but at lest we don't send people into failed transactions so should not be a blocker. Ideally we have some visual pattern to signal to users right after selecting algo that the algo won't work, like dim it, or some tiny warning text on the row.

Case could be also made to hide algos where we know they are not orderable from the AssetSelection here altogether, or dim them, or group them in the list to the bottom with some group header Not Usable or something.

[bogdanfazakas]

awesome, confirmed all prices are in sync in this place now:

Getting this though, but I guess this is actually what we want now when checking for isOrderable?

Bit confusing to users as to what is wrong but at lest we don't send people into failed transactions so should not be a blocker. Ideally we have some visual pattern to signal to users right after selecting algo that the algo won't work, like dim it, or some tiny warning text on the row.

Case could be also made to hide algos where we know they are not orderable from the AssetSelection here altogether, or dim them, or group them in the list to the bottom with some group header Not Usable or something.

yeah that error is displayed when asset is not orderable, in you case it's probably because your dataset is on other provider that the selected algorithm with service type compute
we can add some checks in AssetSelection and pass the dataset provider and not display algorithms with compute services that are using diferent providers in the list

[kremalicious]

haha, this is a product design nightmare. If the restriction of our product is that dataset and algo need to be on the same provider I would be in favor of only showing algos of the same provider in the list. Or we prevent them from showing up when publisher edits compute settings, then we will not run into the issue on the start compute side

[mihaisc]

So you can use an algo from another provider if that algo has an access service not a consume service. Since the filtering is done client side you can remove the algos that have compute service with a different provider

[kremalicious]

can't order anything.

On Rinkeby, trying to combine these, both on same provider:

• https://market-git-feature-sugraph-util-methods-oceanprotocol.vercel.app/asset/did:op:d5766cc73AE44977b4F7d72cDd3b33740101e830
• https://market-git-feature-sugraph-util-methods-oceanprotocol.vercel.app/asset/did:op:49A558D5DeE4b54B7fE4A578996e2Fc4E24847B3

Still giving me:

[bogdanfazakas]

can't order anything.

On Rinkeby, trying to combine these, both on same provider:

• https://market-git-feature-sugraph-util-methods-oceanprotocol.vercel.app/asset/did:op:d5766cc73AE44977b4F7d72cDd3b33740101e830
• https://market-git-feature-sugraph-util-methods-oceanprotocol.vercel.app/asset/did:op:49A558D5DeE4b54B7fE4A578996e2Fc4E24847B3

Still giving me:

Strange, i also got another error for this asset combo, but when trying to buy DT, an oceanjs error 'Not enough Ocean Tokens'

[mihaisc]

you can't buy this https://market-git-feature-sugraph-util-methods-oceanprotocol.vercel.app/asset/did:op:49A558D5DeE4b54B7fE4A578996e2Fc4E24847B3

[mihaisc]

can you add this algo to trusted https://market-git-feature-sugraph-util-methods-oceanprotocol.vercel.app/asset/did:op:F1ffeB5eCA97da9144DC2964A5E2361F0A71DD99

[mihaisc]

but this issue has nothing to do with this pr

[kremalicious]

ah ok, so just tried with that Row count, but get the same. If nothing to do with this PR then I'm fine just moving ahead and merging, and fixing in another PR

[bogdanfazakas]

ah ok, so just tried with that Row count, but get the same. If nothing to do with this PR then I'm fine just moving ahead and merging, and fixing in another PR

can you try again now, for me started working suddenly maybe again some compute env issues

[kremalicious]

nope, but this message seems interesting

ERROR: Algorithm [object Object] is not allowed by did:op:d5766cc73AE44977b4F7d72cDd3b33740101e830

[kremalicious]

I think my bad, testing locally and despite fresh npm install and all still failing. But was able to run successfully on preview version 🥳

Exciting!