hazo_scrape 1.1.0 → 1.2.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGE_LOG.md +6 -0
- package/package.json +1 -1
package/CHANGE_LOG.md
CHANGED
|
@@ -1,5 +1,11 @@
|
|
|
1
1
|
# hazo_scrape — Change Log
|
|
2
2
|
|
|
3
|
+
## 1.2.0 — 2026-07-22
|
|
4
|
+
|
|
5
|
+
### Added — `mapRows` optional `opts.dateFormats`
|
|
6
|
+
- `mapRows(table, map, keywords, opts?)` — new optional 4th parameter, `{ dateFormats?: string[] }`, forwarded verbatim to `parseDate`'s `opts.formats` for every date-typed cell. Purely additive: omitting `opts` preserves the exact prior behavior (a genuinely ambiguous slash date, e.g. `"09/11/2012"`, still resolves to `null` — see the pinned "never guess" test in `__tests__/map_rows.test.ts`).
|
|
7
|
+
- Motivation: a caller that KNOWS a source's date convention (e.g. `extractor_asx`'s `SourceRegistryEntry.nuances.date_formats`, which existed in that consumer's schema but had nothing to plug into) can now pass a `DD/MM/YYYY`/`MM/DD/YYYY` hint through `mapRows` to resolve what would otherwise be an unresolvable ambiguity, without this engine ever guessing on its own.
|
|
8
|
+
|
|
3
9
|
## 1.1.0 — 2026-07-19
|
|
4
10
|
|
|
5
11
|
### Added — fetch layer (`hazo_scrape/fetch`, server-only)
|