pipedream
pipedream copied to clipboard
Fixing folder structure and imports (fixes #3966)
The latest updates on your projects. Learn more about Vercel for Git ↗︎
| Name | Status | Preview | Updated |
|---|---|---|---|
| pipedream-docs | ✅ Ready (Inspect) | Visit Preview | Sep 7, 2022 at 0:51AM (UTC) |
| pipedream-docs-redirect-do-not-edit | ✅ Ready (Inspect) | Visit Preview | Sep 7, 2022 at 0:51AM (UTC) |
Thank you so much for submitting this! We've added it to our backlog to review, and our team has been notified.
Thanks for submitting this PR! When we review PRs, we follow the Pipedream component guidelines. If you're not familiar, here's a quick checklist:
- [ ] Create components to address specific use cases whenever possible
- [ ] Component
keys should follow the formatapp_name_slug-slugified-component-name - [ ] Components should follow the standard directory structure
- [ ] Prefer Node.js client libraries to REST APIs
- [ ] When making API requests, handle pagination to ensure all data / events are processed
- [ ] Use
secretprops to capture sensitive data - [ ] Props and methods should be defined in app files whenever possible
- [ ] Document methods with JS Docs
- [ ] Use
optionalprops whenever possible, and set adefaultvalue where you can - [ ] Use async options to accept user input wherever possible
Hi @bsommardahl, there's a new check for TS components, it will alert if there are any issues regarding the compilation phase. If you merge with master, it will start running for every change in this PR!
Closing since this was done in #4226.