yangzhang75 opened a new issue, #6054:
URL: https://github.com/apache/texera/issues/6054
### What happened?
Typing into an integer operator property (reproduced on the Limit operator's
"Limit"
field) stops updating the value — it gets stuck (e.g. at 1). The up/down
stepper
buttons still work; only typed input is broken.
Root cause (verified in the browser console): @ngx-formly/core's json-schema
integer
parser runs on value change and does:
const input = document.querySelector(`#${f.id}`);
if (input && !input.validity.badInput) { ... } //
ngx-formly-core-json-schema.mjs:153
But the field id is applied to ng-zorro's <nz-input-number> host element,
not the
inner native <input>. The host has no `.validity`, so `input.validity` is
undefined
and `.badInput` throws:
TypeError: Cannot read properties of undefined (reading 'badInput')
at field.parsers (ngx-formly-core-json-schema.mjs:153:58)
...
updateValue (ng-zorro-antd-input-number.mjs:262)
setValueByTyping (ng-zorro-antd-input-number.mjs:239)
onInput (ng-zorro-antd-input-number.mjs:323)
The parser branch only runs when the parsed value is null (which typing can
produce
as an intermediate state), so typing throws and the value never commits —
while the
stepper always sends a concrete number, skips the branch, and works.
Expected: integer/number fields stay editable by typing.
### How to reproduce?
1. Add a Limit operator; open its property panel; open the browser devtools
console.
2. Type a value into "Limit" (or set a negative value and run) — the value
gets stuck
and the console shows the TypeError above.
3. The +/- stepper buttons still change the value; typing does not.
https://github.com/user-attachments/assets/26447a20-6c92-4ea2-beab-8e7544d64368
### Version/Branch
1.3.0-incubating-SNAPSHOT (main)
### Commit Hash (Optional)
_No response_
### What browsers are you seeing the problem on?
_No response_
### Relevant log output
```shell
```
--
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]
