laboratory
laboratory copied to clipboard
List of Suggestions
This is a list of things that we might consider to implement at the end of the v2 development.
- [Development] should we save the entire
networkinformation in the url parameters? We might need to display all of the information forcustomnetwork. However,TESTNET,MAINNET, andFUTURENETdo not allow configuration to these fields so we might not need to display all of that (our old lab displays only the network id). - [Design for Endpoints] It would be nice to have a clear instruction about filters. At least one of the fields is required, but we mention in the labels that they're optional. Let's come back to this after implementing required forms.
- [Design for Muxed Account] It would be nice to include this doc which is much friendlier bersion than
CAP27andSEP23 - Path Endpoint: this is how the current lab works as well. But ideally,
destination_assetshouldn't display an error by default -
validate.amount: it accepts leading zero but horizon corrects it. frontend should follow what horizon does. - Ledger's error
Missing critical parameterto be more specific (slack msg) - analytics