aglinxinyuan opened a new pull request, #8922: URL: https://github.com/apache/texera/pull/8922
### What changes were proposed in this PR? Removes two module-level constants from `operator-metadata.service.ts` that nothing reads: `addDictionaryAPIAddress` and `getDictionaryAPIAddress`. **−3 lines.** There is no behaviour change. The constants aren't exported, their URL strings (`/api/resources/dictionary/`, `/api/upload/dictionary/`) appear nowhere else, and the backend has no route at either path. `OPERATOR_METADATA_ENDPOINT`, which the service does use, stays. ### History | | | | --- | --- | | **Introduced by** | #696 (merged 2019-06-07), "Add saved project and dictionary upload components in user panel" | | **Usage removed by** | **never used**. No line has ever read either constant. Later removals of similar dictionary URLs (e.g. in `user-dictionary.service.ts`) were different constants | They have been unused for over six years. ### Any related issues, documentation, discussions? Closes #8921 ### How was this PR tested? No new tests; nothing referenced the constants. From `frontend/`: - `npx ng test --watch=false`, covering `operator-metadata.service.spec.ts` plus the 40 other jsdom specs that import the service: 1846 tests pass, 1 is skipped (an existing `it.skip`). - `npx ng run gui:test-browser --watch=false --include='**/code-editor.component.browser.spec.ts'` (the one browser spec that imports it): 11 tests, all pass. - `yarn format:ci`: clean. - `npx ng build`: success. To re-check: ``` git grep -n -e DictionaryAPIAddress -e "resources/dictionary" -e "upload/dictionary" # no hits ``` ### Was this PR authored or co-authored using generative AI tooling? Generated-by: Claude Code (Claude Opus 5.5) 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- 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]
