| Is the SPA ready for this? What is left here? | |
| SPA support and testing with betel+rusty is missing. Do we need SPA support for 1.5? | |
| i would say yes, hacking this in is otherwise too brittle IMO: someone edits in the spa, hits submit and the setting is gone would be bad. | |
| Anyway, Sebastian marked 0011120 already as 'fixed', so does the SPA already support it? | |
| we shouldn't trust him. This is the screen and this is the request produced curl 'https://merchant.taler/private/accounts' \ -H 'Accept: application/json' \ -H 'Accept-Language: en-US,en;q=0.9' \ -H 'Authorization: Bearer secret-token:MJ0MZ9BV27BK463Y2FX7WC4BR856MMZDG0VYQQVBAMJHVV3C9V80' \ -H 'Cache-Control: no-cache' \ -H 'Connection: keep-alive' \ -H 'Content-Type: application/json' \ -H 'Origin: https://dev.taler' \ -H 'Pragma: no-cache' \ -H 'Referer: https://dev.taler/' \ -H 'Sec-Fetch-Dest: empty' \ -H 'Sec-Fetch-Mode: cors' \ -H 'Sec-Fetch-Site: cross-site' \ -H 'Taler-Challenge-Ids: 72-TVRGPZSF95P9N24F4QHBHVVJ8A6X5AR1KR3CNYNDPXD097FNH21G' \ -H 'User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/139.0.0.0 Safari/537.36' \ -H 'sec-ch-ua: "Chromium";v="139", "Not;A=Brand";v="99"' \ -H 'sec-ch-ua-mobile: ?0' \ -H 'sec-ch-ua-platform: "Linux"' \ --data-raw '{"payto_uri":"payto://iban/DE15970186998345619168?receiver-name=alfred","extra_wire_subject_metadata":"THEend123"}' image.png (33,820 bytes) image-2.png (23,666 bytes) | |
| Looks reasonable... (I wonder if we should allow spaces...). | |
| We don't allow spaces, and Sebastian's validation is also in alignment with that. Adding spaces would make the wire transfer subject harder to parse IMO. | |
| Tested with rusty (all steps except the final submission of the transaction via EBICS). | |
- Anonymous