Commit f1588ae
committed
docs(waterdata): Frame _NEVER_CHUNK as exceptions to a default-chunk rule
After investigating: the OGC getters expose ~94 list-shaped params, all
chunkable. The current 13-entry denylist captures every exception. An
allowlist would be ~7x longer and would need updating every time USGS
adds a column.
Reframe the comment to state the default rule first ("any list-shaped
kwarg gets chunked"), then enumerate the exceptions by reason
(response-shaping, structured, intervals, handled-elsewhere, scalar-by-
contract). Reads as "here are the few cases the default-chunk rule
doesn't apply" rather than "here is an arbitrary exclusion set."1 parent ee550be commit f1588ae
1 file changed
Lines changed: 12 additions & 7 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
51 | 51 | | |
52 | 52 | | |
53 | 53 | | |
54 | | - | |
55 | | - | |
56 | | - | |
57 | | - | |
| 54 | + | |
| 55 | + | |
| 56 | + | |
| 57 | + | |
| 58 | + | |
| 59 | + | |
| 60 | + | |
| 61 | + | |
58 | 62 | | |
59 | 63 | | |
60 | 64 | | |
61 | | - | |
62 | | - | |
63 | | - | |
| 65 | + | |
| 66 | + | |
| 67 | + | |
| 68 | + | |
64 | 69 | | |
65 | 70 | | |
66 | 71 | | |
| |||
0 commit comments