Docstrings clarification#466
Conversation
Greptile SummaryThis PR adds a single docstring note to
Confidence Score: 3/5The only change is a docstring note that contradicts the actual implementation — merging it would publish incorrect usage guidance to library consumers. The added NOTE tells callers to pass uniswap/uniswap4.py — specifically the new NOTE in the Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A["Caller passes path=[A,B,C] (forward order)"]
B["encode_path_keys_output"]
C["reversed(path) → [C,B,A]\nreversed(hook_data_list)"]
D["Per iteration: compute currency_in\nbuild PathKey\ninsert at index 0"]
E["encoded_path = [PathKey_A, PathKey_B, PathKey_C]\n(forward order restored)"]
F["Returned to quoter"]
A --> B --> C --> D --> E --> F
note1["⚠️ Docstring NOTE claims caller must pass\npath in REVERSE order — this is incorrect.\nDouble-reversal means forward order is correct."]
D -.-> note1
Reviews (1): Last reviewed commit: "Docstrings clarification" | Re-trigger Greptile |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## dev/v4-fin #466 +/- ##
===============================================
- Coverage 76.83% 39.76% -37.07%
===============================================
Files 12 12
Lines 2253 2253
===============================================
- Hits 1731 896 -835
- Misses 522 1357 +835 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
No description provided.