aglinxinyuan opened a new pull request, #7030:
URL: https://github.com/apache/texera/pull/7030

   ### What changes were proposed in this PR?
   
   Deletes three frontend files that nothing references. Pure deletion, no 
behaviour change: **−146 lines**.
   
   | Removed | Lines | Why it is dead |
   | --- | ---: | --- |
   | `workspace/component/left-panel/environment/environment.component.ts` | 18 
| contains only the ASF license header — zero statements |
   | `common/util/map.ts` | 42 | `mapToRecord` / `recordToMap` have no caller |
   | `common/util/map.spec.ts` | 86 | covers only the above |
   
   `environment.component.ts` has no class, no decorator and no exports, so it 
cannot be declared in a module, matched by a selector, or loaded by a route. It 
was the only file in `environment/`, so that directory goes too.
   
   `map.ts` predates `Object.fromEntries` and `new Map(Object.entries(...))`, 
both already available under the project's `lib: ES2022` setting, so nothing 
needs to replace it. Its spec was added by #6621, which is why the util 
currently looks live.
   
   ### Any related issues, documentation, discussions?
   
   Closes #7029
   
   ### How was this PR tested?
   
   Existing tests only — this PR adds none, since it removes files and the spec 
that covered them.
   
   - `npx tsc --noEmit -p frontend/tsconfig.json` — exit 0, confirming no 
dangling imports.
   - Checked that no build or test config enumerates the deleted paths 
(`angular.json`, `tsconfig*.json`, `src/test.ts`).
   
   Verification that nothing references the removed code, re-runnable by a 
reviewer:
   
   ```
   grep -rn "mapToRecord\|recordToMap\|EnvironmentComponent" frontend/src 
--include=*.ts --include=*.html --include=*.json
   ```
   
   ### Was this PR authored or co-authored using generative AI tooling?
   
   Generated-by: Claude Code (Claude Opus 5)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to