`forceInput` Doesn't maintain input order
Open
Bug
- Dominant language
- Python
- Stars
- 133k
- Forks
- 15.7k
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 158
Description
Using `forceInput` for a node's input doesn't maintain its order on the node's input slots. Looks like it's always added as a widget, and then later converted to an input, which puts it at the end of the input list.
Especially as a `forceInput` where it's meant to just be an input from the start (and can't be converted back to a widget).
Contributor guide
Assessment
This issue has not been assessed yet.