PipedreamHQ
Google Drive Triggers text/usability improvements
- Adjusted several text descriptions;
- Removed the 'Watch for Properties Changes' prop from several sources, except 'New or Modified Files';
- Added a 'Minimum Interval' prop to the sources that trigger on file modifications. This allows the user to set a minimum interval for events to be emitted for the same file, defaulting to 1 minute, and can be disabled using 0.
The latest updates on your projects. Learn more about Vercel for Git ↗︎
3 Ignored Deployments
| Name | Status | Preview | Comments | Updated (UTC) |
|---|---|---|---|---|
| docs-v2 | ⬜️ Ignored (Inspect) | Visit Preview | May 7, 2024 4:55pm | |
| pipedream-docs | ⬜️ Ignored (Inspect) | May 7, 2024 4:55pm | ||
| pipedream-docs-redirect-do-not-edit | ⬜️ Ignored (Inspect) | Visit Preview | May 7, 2024 4:55pm |
![vercel[bot] avatar](https://avatars.githubusercontent.com/in/8329?v=4 "Published by a pub.dev verified publisher"){kind=small}
Hello everyone, I have tested this PR and there're some test cases failed or needed improvement.
Please check the test report below for more information https://vunguyenhung.notion.site/Google-Drive-Triggers-text-usability-improvements-11652-6cdfb734841c4efcb09d4d111cc76260
@vunguyenhung , as I understand it, these sources are also triggered for new files/folders, or in other situations that do not necessarily have 'changes' to be emitted - do you think we should emit an empty 'changes' object to maintain the schema in this case?
Hey @GTFalcao, yes I think we could either modify the initial events to have empty change/changes field, or remove them altogether
Hi everyone, all test cases are passed! Ready for release!
Test report https://vunguyenhung.notion.site/Google-Drive-Triggers-text-usability-improvements-11652-6cdfb734841c4efcb09d4d111cc76260
Hi everyone, all test cases are passed! Ready for release!
Test report https://vunguyenhung.notion.site/Google-Drive-Triggers-text-usability-improvements-11652-6cdfb734841c4efcb09d4d111cc76260