You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@texera.apache.org by "kz930 (via GitHub)" <gi...@apache.org> on 2026/08/07 23:21:12 UTC
[I] Clearing a text property in the operator panel does not take effect — the operator keeps the previous value [texera]
kz930 opened a new issue, #7394:
URL: https://github.com/apache/texera/issues/7394
### What happened?
The property panel's text inputs never write an empty value back to the operator. Clearing a field leaves the box empty on screen while the operator keeps whatever it held before, so the workflow runs on a value the user can no longer see.
Reproduced against CSV File Scan's Delimiter, reading the stored operator properties after each step:
| step | box shows | operator holds |
| --- | --- | --- |
| freshly dropped | `,` | `","` |
| cleared, waited 3s | empty | `","` |
| typed `X`, waited 3s | `X` | `"X"` |
| cleared again, waited 4s | empty | `"X"` |
| clicked away to blur the field, waited 3s | empty | `"X"` |
Typing arrives within three seconds, so the change stream and its 150 ms debounce are working. Only the empty value fails to arrive, and blurring does not help. The panel and the executed workflow therefore disagree: the box is empty while the file is parsed on `X`. It also means an empty string is unreachable from the UI for any text property, including the ones where empty is meaningful.
Either behaviour would be acceptable as long as the panel reflects it — write the schema default back and display it, or keep the last valid value and display it. What is wrong is that the retained value is invisible.
The root cause is not identified. `onFormChanges` (`operator-property-edit-frame.component.ts:546`) strips only `null` and `undefined`, so `""` should pass; `distinctUntilChanged` cannot block it because a fresh object is built on every event; `checkOperatorProperty` compares with `isEqual`, and `""` differs from the old value. Something between the formly model and that handler drops it.
Not every control is affected: Bubble Chart's Color Column, a dropdown with no schema default, does store an empty string when cleared. The behaviour above was observed on plain text inputs.
### How to reproduce?
1. Create a workflow and drop a CSV File Scan.
2. Delimiter shows its default `,`. Type `X` and wait a moment — the operator now holds `X`.
3. Clear the field and click elsewhere to blur it.
4. The box is empty and the operator still holds `X`. Reload the page and `X` comes back.
### Version/Branch
1.3.0-incubating-SNAPSHOT (main)
### Commit Hash (Optional)
e7cd5b1ee
### What browsers are you seeing the problem on?
Chrome
### Relevant log output
_No response_
--
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: notifications-unsubscribe@texera.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Clearing a text property in the operator panel does not take effect — the operator keeps the previous value [texera]
Posted by "aglinxinyuan (via GitHub)" <gi...@apache.org>.
aglinxinyuan closed issue #7394: Clearing a text property in the operator panel does not take effect — the operator keeps the previous value
URL: https://github.com/apache/texera/issues/7394
--
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: notifications-unsubscribe@texera.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Clearing a text property in the operator panel does not take effect — the operator keeps the previous value [texera]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #7394:
URL: https://github.com/apache/texera/issues/7394#issuecomment-5223151001
<!-- texera:template-compliance -->
👋 Thanks for opening this issue, @kz930!
It looks like the issue description doesn't quite follow our template yet:
- This issue doesn't appear to use one of our templates (Bug, Feature, or Task). Please open it using a template so the required details are captured.
Filling out the template helps reviewers understand and triage your contribution faster. Please edit the description to complete it. This message will disappear automatically once the template is followed.
You can find the template prompts by editing the description, or see [CONTRIBUTING.md](https://github.com/apache/texera/blob/main/CONTRIBUTING.md) for the full contribution flow.
--
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: notifications-unsubscribe@texera.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org