Closed meganrm closed 11 months ago
St.:grey_question: |
Category | Percentage | Covered / Total |
---|---|---|---|
π‘ | Statements | 74.94% (+0.1% πΌ) |
589/786 |
π‘ | Branches | 70.18% (+0.53% πΌ) |
80/114 |
π΄ | Functions | 42.16% (+0.31% πΌ) |
78/185 |
π‘ | Lines | 73.5% (+0.07% πΌ) |
527/717 |
99 tests passing in 7 suites.
Report generated by π§ͺjest coverage report action from 4d0ee6734b22d702415b9621c502e68953eb1a00
Problem
Closes #436
Solution
The binary between "networked file" and "local file" is not exactly what we needed for if a file is sharable. "networked" means it is hosted on our server, "local" means it's been loaded into local memory. When you load a file that is hosted on dropbox or other cloud storage, it's technically "local" because it's stored in local memory, but it is still shareable. So I made a new utility function that just checks that there is url param for either a networked file or a cloud storage file.
One additional change: I was checking other places we are differentiating between the two just to make sure there wasn't the same problem elsewhere and I saw that we were using a type guard to check if a file is networked, but we had a more extensive check as a selector, so I swapped those.
Type of change
Please delete options that are not relevant.
Steps to Verify:
npm start
Screenshots (optional):