yangzhang75 opened a new issue, #8439: URL: https://github.com/apache/texera/issues/8439
Two minor refinements surfaced in review of the input-rendering PR (#8437, sub-issue #8370). Both are out of scope for the MVP; filing so they are not lost. Part of the Form View feature (#8011). ### 1. Full HuggingFace form-view mode An exposed HuggingFace model picker (`modelId`) now gets the operator's other properties (including `task`) as read-only context, so it loads the right models and labels the field correctly, and only the bound property is written back. What is not yet handled: the widget's own task selector is still interactive, and a task change is not persisted (the form writes back only the bound property), so a reader could in principle pick a model/task pair the operator's real task does not match. A proper form-view mode for the widget would use the provided task and hide/lock the task selector, so only the model is chosen. This touches the shared `hugging-face.component`, which is why it is deferred out of the render slice. ### 2. Compilation update dropped while the reader is typing The inputs rebuild on the compilation-state stream, and the rebuild is skipped while the reader is typing so it does not throw away a half-entered value. The stream is a `ReplaySubject(1)`, so a state update that arrives during typing is dropped and not replayed once focus leaves the field. If that update carried new upstream column names, an attribute control stays a plain text box until some unrelated compilation fires. The fix is to record a pending rebuild and flush it on blur. -- 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]
