chore(data): drop stale August 9 baseline JSON - #17
Conversation
Both deploy workflows scrape fresh data before building, so the committed src/data/antalya.json is only a liability: its Aug 9 snapshot is what shipped when a push deploy skipped the scraper (documented in deploy.yml). - delete src/data/antalya.json, git-ignore src/data/*.json so a stale baseline can never be committed again - CityPage resolves city data via import.meta.glob at build time; a fresh clone without scraped data builds into a localized empty state (noData strings for tr/en/de/ru) instead of failing - README: describe deploy-time scraping, drop baseline instructions Verified: build succeeds with no data file (empty state rendered, no pharmacy rows) and with scraped data (39 pharmacies + fresh timestamp).
|
@coderabbitai review |
✅ Action performedReview finished.
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (7)
💤 Files with no reviewable changes (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe deployment documentation now describes scrape-before-build behavior. The committed Antalya dataset is removed. ChangesGenerated Data Handling
Priority: ⬇️ Low Estimated code review effort: 3 (Moderate) | ~20 minutes Merge Risk: ⚪ Minimal · up to This change removes stale committed city data and lets builds render a localized no-data state until fresh scraped data is available. The current implementation is ready to merge. Sequence Diagram(s)sequenceDiagram
participant CityPage
participant GlobData as import.meta.glob
participant MapView
participant I18n
CityPage->>GlobData: resolve city JSON
GlobData-->>CityPage: data or undefined
CityPage->>I18n: read noData translation
CityPage->>MapView: pass pharmacies or []
CityPage-->>CityPage: render update time or no-data message
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
🟢 Approval recommended
The changes align with the documented deploy workflows (both scrape before building) and the code now builds cleanly with or without local scraped JSON present.
Pull request overview
This PR removes the committed Antalya scrape baseline and updates the build to gracefully handle the absence of scraped data, relying on deploy-time scraping in GitHub Actions instead of repo-committed JSON.
Changes:
- Deleted
src/data/antalya.jsonand addedsrc/data/*.jsonto.gitignore(keeping the directory tracked via.gitkeep). - Updated
CityPage.astroto load scraped JSON viaimport.meta.globat build time and render a localized empty state when data is missing. - Added localized
noDatastrings and updated README guidance to explicitly forbid committed baselines.
File summaries
| File | Description |
|---|---|
| src/styles/global.css | Adds styling for the new “no data” empty-state message. |
| src/lib/i18n.ts | Introduces noData string and provides translations for all locales. |
| src/data/antalya.json | Removes the stale committed baseline scrape data. |
| src/data/.gitkeep | Keeps src/data/ tracked while ignoring generated JSON files. |
| src/components/CityPage.astro | Switches from static JSON import to build-time glob resolution + empty-state rendering. |
| README.md | Updates deployment documentation to reflect deploy-time scraping and forbid committed baselines. |
| .gitignore | Prevents future scraped JSON baselines from being committed. |
Review details
- Files reviewed: 5/7 changed files
- Comments generated: 0
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Summary
Drops the committed stale baseline
src/data/antalya.json(scraped 2026-08-09) and makes the site build without any committed data.Both deploy workflows scrape fresh data before building, so the committed baseline is only a liability — it's exactly what shipped when a push deploy skipped the scraper (documented in
deploy.yml: the 2026-09-09 regression to August data).Changes
src/data/antalya.json; git-ignoresrc/data/*.json(with.gitkeep) so a stale baseline can never be committed againCityPage.astroresolves city data viaimport.meta.globat build time; a fresh clone without scraped data builds into a localized empty state (newnoDatastrings for tr/en/de/ru) instead of failingVerification
npm run buildwith no data file: succeeds, renders the localized empty state, no pharmacy rowsnpm run buildafternpm run scrape -- antalya: renders 39 pharmacies with a fresh last-updated timestamp🤖 Generated by an agent (Codex) — opened via vekili as
vekilibot[bot].Summary by CodeRabbit
New Features
Bug Fixes
Documentation
Chores