fix(jobdanmark-search): emit the /scrape contract fields in search output (#340)

Adds additive normalization so jobdanmark search output carries the cross-portal contract fields: company from companyName, location as the city after the postal code in companyAddress (null-safe - a missing or null address yields null instead of crashing the search), and date/deadline converted from DD-MM-YYYY to YYYY-MM-DD with safe passthrough on unexpected formats. Native fields unchanged.

Co-authored-by: oscarbol09 <80536682+oscarbol09@users.noreply.github.com>
This commit is contained in:
Oscar Madera
2026-08-19 08:32:06 +02:00
committed by GitHub
parent 04186b9a37
commit 17bc698697
4 changed files with 89 additions and 4 deletions
+7
View File
@@ -46,6 +46,13 @@ per-file diff commands.
### Fixed
- **`jobdanmark-search` search output now carries the `/scrape` contract fields** - the CLI
exposed the API-native schema (`companyName`, `publishedDate` in `DD-MM-YYYY`, …) with no
`company`, `location`, `date` or `deadline`, so every `/scrape` run flagged jobdanmark as
degraded and the `seen_jobs.json` dedupe lost the company. Search results now additively emit
`company`, `location` (city after the postal code in `companyAddress`), and `date`/`deadline`
in the `YYYY-MM-DD` convention, with null-safe handling of a missing address.
- **`jobnet-search` search output now carries the `/scrape` contract fields** - the CLI emitted
the raw Jobnet API schema (`jobAdId`, `hiringOrgName`, `publicationDate`, …) with no
`company`, `location`, `date` or `url`, so every `/scrape` run flagged jobnet as degraded