fix(connectors): attribute SharePoint not-found errors to the matched library - #6029
Conversation
… library When the first path segment named a real non-default document library but the remainder did not resolve there, the failure message described a search of the default library over the full original path, and advised stripping a library prefix the user had supplied correctly. Report against the library that was matched, over the remainder that was actually searched, and only suggest omitting a leading library name when the default library really was the one searched.
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
PR SummaryLow Risk Overview
Regression tests cover the matched-library case and confirm the prefix hint still appears for paths like Reviewed by Cursor Bugbot for commit 01a136d. Configure here. |
Greptile SummaryFixes SharePoint folder not-found diagnostics so they attribute the matched library and remainder path, and only suggest stripping a Documents/Shared Documents prefix when the default library was actually searched.
Confidence Score: 5/5This PR appears safe to merge; no blocking failures remain from the current change set or prior review findings available in this session. No blocking failure remains. The update only corrects diagnostic attribution and when the prefix-stripping hint is shown; resolution behavior is unchanged and covered by new tests.
|
| Filename | Overview |
|---|---|
| apps/sim/connectors/sharepoint/sharepoint.ts | Attributes not-found errors to the matched library and remainder path; gates the Documents/Shared Documents prefix hint on default-library search. |
| apps/sim/connectors/sharepoint/sharepoint.test.ts | Adds regression coverage for matched-library blame and default-library prefix-hint behavior. |
Reviews (2): Last reviewed commit: "fix(connectors): key the library-prefix ..." | Re-trigger Greptile
…searched
Deriving the flag from `!libraryMatch` suppressed the hint when the path named
the default library itself ("Documents/Reports"), which is exactly the case the
hint exists for. Key it on whether the reported drive is the default library.
|
@cursor review |
There was a problem hiding this comment.
✅ Bugbot reviewed your changes and found no new issues!
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit 01a136d. Configure here.
Summary
Follow-up to #6026, fixing a Cursor Bugbot finding that was reported before that PR merged but landed unfixed.
buildFolderNotFoundMessagedescribed a search of the default library over the full original pathDocuments/Shared Documentsprefix — actively wrong when the user had correctly supplied a library nameConcretely:
Policies/HR, wherePoliciesis a real library andHRis not in it, previously reporteddocument library "Documents"and path"Policies/HR"and listed the wrong library's folders. It now namesPolicies, the pathHR, and lists that library's folders.Diagnostics only — no change to which folder resolves.
Type of Change
Testing
Added a regression test asserting the message names the matched library, its remainder, and its folder names, and contains neither the default library name nor the prefix hint. 23 connector tests pass; typecheck and lint clean.
Checklist