Databases are fetched each and every time the dropdown select of the form mounts, which makes it fairly inefficient.
Solution
Launch
When a user uses the extension for the first time, and the dd select mounts, it should obviously look for eligible Notion databases. When that happens:
[ ] Databases that've been found should be saved in the extension's storage
Run
Afterwards, we should only fetch eligible databases when:
[ ] There are no db in the storage yet
[ ] The user manually asks for a database refresh from the side panel (to handle cases where he created and/or shared a new eligble db with the integration)
Resources
TODO: design wireframes in Figma to spec the new 'refresh db' (🔄) button.
Context
Databases are fetched each and every time the dropdown select of the form mounts, which makes it fairly inefficient.
Solution
Launch
When a user uses the extension for the first time, and the dd select mounts, it should obviously look for eligible Notion databases. When that happens:
Run
Afterwards, we should only fetch eligible databases when:
Resources