Repository navigation
Name the content location when find targets are ambiguous #11
Description
Activity
I’m planning the narrow ambiguity-message fix: show each candidate’s
FindHit.Locationwhen it is available while preserving the current candidate wording for hits without a location.Hi @aryansk, are you still working on this? Your plan (show each candidate's
FindHit.Locationand keep the current wording for hits without one) is still the right fix, and it pairs naturally with #10. If you are, just say so and it stays yours. If I don't hear back by October 10, I'll unassign it so someone else can pick it up during Hacktoberfest. You're welcome to take it again later. Saying "I can't get to this" is completely fine too.
Problem you're trying to solve
edit_documentaccepts"target": { "find": "Acme Corp" }and resolves it against live content. When the text matches more than once,FindTargetResolverrefuses the operation and lists the candidates so the agent can resend with"match": <index>.Right now agent is not able distinguish between matches from different part of document.
Proposed shape
Include the location in each candidate when the hit has one, and leave the line unchanged when it does not.