Repository navigation
Fix(assistant): Use context.fileid instead of context.data.id - #684
Conversation
The Folder context passed by addNewFileMenuEntry exposes the folder ID via the .fileid getter, not .data.id, causing a TypeError on submit. Signed-off-by: Aliza Held <aliza.held@strato.de>
fc3b2d6 to
69b522f
Compare
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (1)
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe scheduled image task’s Priority: ⬇️ Low Merge Risk: ⚪ Minimal · up to The scheduled image task now uses the Folder’s supported ID getter. The checked menu paths provide numeric folder IDs, and no actionable merge-blocking risk remains. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
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. Comment |
julien-nc
left a comment
There was a problem hiding this comment.
Thanks a lot! This issue comes from a change in@nextcloud/files >= v4.0.0
The Folder context passed by addNewFileMenuEntry exposes the folder ID via the .fileid getter, not .data.id, causing a TypeError on submit.
🤖 AI (if applicable)