mavo mv-init backend should not log in if source has data

mv-init backend should not log in if source has data

Open LeaVerou opened this issue 3 years ago • 2 comments

Right now, mv-init triggers requests for authentication, even if it will never be used for data because mv-source includes data.

Testcase: https://codepen.io/leaverou/pen/xxWJKJR?editors=1100 (open Network panel of dev tools, you will see the requests to the GitHub API)

Aug 09 '22 11:08 LeaVerou

If the storage backend implements permissions, it needs to authenticate? Is it supposed to assume read access?

Aug 09 '22 13:08 joyously

mv-init is not even relevant if source/storage have data. It doesn't matter what permissions it has.

Aug 09 '22 15:08 LeaVerou