Making asset unavailable for purchase if the size is zero

[jamiehewitt15]

Closes:

Changes proposed in this PR:

• Checking if the file size is 0
• Making the asset unavailable if the file size is zero

[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/6iU2eN1MapMFARM7eq1tN8i9XJmD
✅ Preview: https://market-git-issue-581-file-length-check-oceanprotocol.vercel.app

[codeclimate]

Code Climate has analyzed commit 35f3c46 and detected 0 issues on this pull request.

View more on Code Climate.

[kremalicious]

file here refers to the file metadata object within the DDO, which is only set upon publish, retrieved when file is added in publish form. So this check here would only kick in if file has been published with contentLength: 0 which is very unlikely

[bogdanfazakas]

I think we can use this provider POST method (https://docs.oceanprotocol.com/references/provider/#apiv1servicesfileinfo) to get the file Content-Type and Content-Length using the asset did

[kremalicious]

Feels like this is generally a better direction for solving #452, which could make #463 obsolete. If we can figure out file availability automatically by hitting the respective provider endpoint (instead of basing logic on fixed file metadata) then we can remove button as is done in this PR. If we have this there would not be much reasons to have publisher pay gas fees to manually disable/enable the button.

Likewise, this PR could be combined with #479

[kremalicious]

As outlined in #479 we can't rely on content-length being correct all the time as it looks like. Considering this, informing user instead of disabling action in #479 seems like a better direction so closing this