Closed hitesh-1997 closed 21 hours ago
As we discussed last week, let's aim to keep PRs focused on a single key change. This will make them easier to review and help reduce the risk of regressions.
This PR could be split into a series of changes that build on each other. For example, we could start by updating the implementation of the
UnifiedDiffStrategy
with the relevant interfaces (inDefaultContextStrategyFactory
andContextRetrieverDataCollection
). After that, we can introduce one new diff strategy per PR: firstTwoStageUnifiedDiffStrategy
, thenLineLevelDiffStrategy
. The changes to prompt utils andRecentViewPortRetriever
seem relatively independent and could also be extracted into smaller, separate PRs out of the stack.I know it's not fun to spend time on this "extra" work, but we need to make it a habit from the get-go. This PR could be a great place to start. Holding each other accountable will make it easier to iterate faster in the long run.
Refactored the PR into several other PRs. Closing this one.
Context
The PR makes the following high-level changes:
10 sec
diff data by the user in the analytics to capture the short term diffs.Test plan
Added Unit tests for various changes