chore(data): remove legacy source layout and freeze Fly deploy#231
Conversation
|
Important Review skippedToo many files! This PR contains 300 files, which is 150 over the limit of 150. To get a review, narrow the scope: ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (300)
You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 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 |
5c09475 to
2b37459
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 2f993d11a3
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
@codex review |
|
Codex Review: Didn't find any major issues. What shall we delve into next? ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
Summary
data/source/tree now that canonical target-layout data validatesnpm run data:validateto validate canonicaldata/and addnpm run fixtures:validateWhy
The migrated target data now has coverage parity with the legacy source issue set. Keeping
data/source/and the active Fly deploy path around would keep reviewers and CI tied to a layout that is no longer canonical. The Fly workflow is frozen because the legacy production build path still depends on the removed source layout; full runtime/API/DuckDB cleanup remains Step 8.Validation
npm run checknpm run build:packagesnpm run typechecknpm testnpm run test:packagesnpm run data:validatenpm run fixtures:validatenpm run pages:buildCanonical validation counts: 230 stations, 11 lines, 34 services, 3 operators, 46 towns, 397 landmarks, and 758 issues.