Hello, I have a custom node with an options input type. When a specific option is selected, it deploys a fixed collection input type. The issue is that although the fixed collection is displayed correctly, two additional fixed collection input types appear at the top of the interface. These duplicate inputs copy what I type in the correct fixed collection input
Something to add, this happens only if I choose a custom asset in the Destination part, I don’t have the same problem if I choose a custom asset for the Source
That was a fun little journey and the quick version is you have 3 fields all set to show if isDestinationAssetNative is [false] the 2 that are appearing I suspect are from payments/pathPaymentStrictSend and payments/pathPaymentStrictReceive if you were to load those 2 and set the Destination Asset to Custom Asset you should see the same issue. Quickest way to fix it would be to add another show on the field so it only shows for the operation and resource you are using.
The way I found this was in your screenshot the 2 extra fields appear between Resource and Operation and your description files set the Operation value so we know that the issue is in a file before the Swap description is loaded.
In the code there are only 3 descriptions loaded before it which helped narrow it down, From there it was just a case of greping the code to find isDestinationAssetNative: [false] in those folders and work back from that.
