Yicong-Huang opened a new pull request, #5975: URL: https://github.com/apache/texera/pull/5975
### What changes were proposed in this PR? `FormlyRepeatDndComponent` is a Formly custom field type, registered as `repeat-section-dnd` in `formly-config.ts` and instantiated dynamically by Formly at runtime. Its selector `texera-formly-repeat-section-dnd` never appears in any template, so listing it in a standalone component's `imports` array is redundant — and the Angular compiler emits one warning per component: ``` NG8113: FormlyRepeatDndComponent is not used within the template of <Component> ``` This PR removes the redundant import (the `import` statement and the `imports`-array entry) from the 10 standalone components that listed it, plus the matching NgModule import in `app.module.ts`. The class is still imported and registered via `formly-config.ts`, which is the bundling anchor, so Formly continues to render `repeat-section-dnd` fields at runtime — no behavior change. I also audited the other Formly dynamically-instantiated types/wrappers (`CodeareaCustomTemplateComponent`, `UiUdfParametersComponent`, `PresetWrapperComponent`, `CollabWrapperComponent`, etc.); `FormlyRepeatDndComponent` was the only one with stray standalone imports. `PresetWrapperComponent` is imported in `operator-property-edit-frame` but legitimately used via its static `setupFieldConfig` (not in the `imports` array), so it is left untouched. ### Any related issues, documentation, discussions? Closes #5974 ### How was this PR tested? Static change only — removal of confirmed-unused imports. Verified the selector `texera-formly-repeat-section-dnd` is not referenced in any template and the symbol had no other usage in the affected files. Covered by existing build/CI. 🤖 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]
