-
Notifications
You must be signed in to change notification settings - Fork 5.5k
Configure file stash sync: Adobe PDF Services-Guru #17361
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Adds dir props to relevant components for apps starting with 'A' to 'G'. The 'dir' prop indicates that a stash ID should be passed when running these actions via the Connect API. This allows files written to the ephemeral /tmp directory in one action to be read by another, separately executed action since both can sync /tmp with the same File Stash directory.
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 3 Skipped Deployments
|
|
Important Review skippedMore than 25% of the files skipped due to max files limit. The review is being skipped to prevent a low-quality review. 37 files out of 144 files are above the max files limit of 100. Please upgrade to Pro plan to get higher limits. You can disable this status message by setting the ✨ Finishing Touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
When a component imported a package with pinned version, the "Check component app prop" PR check failed because Node.js was unable to resolve the package version correctly. This commit adds a custom loader that strips the version from the imported package, allowing the check to pass. For example, if the component imports `[email protected]`, the loader will transform the import to `got`.
What
When a component imported a package with pinned version, the "Check component app prop" PR check failed because Node.js was unable to resolve the package version correctly.
For example, if the component has the line,
import got from "[email protected]", check would fail with the following error:WHY
The 'dir' prop indicates that a stash ID should be passed when running these actions via the Connect API. This allows files written to the ephemeral
/tmpdirectory in one action to be read by another, separately executed, action since both can sync/tmpwith the same File Stash directory.