| Sebastian already implemented it in wallet-core. Is it also supported in the UI? I also wonder if we should have an integration test. | |
| fixed at 974cd0206 | |
Selection_086.png (41,596 bytes) | |
| the list of numbers is serialized by the merchant to a string separated by \n this is not standard comma separated is better or maybe just a simple array of numbers instead of string https://docs.taler.net/core/api-merchant.html#post-[-instances-$INSTANCE]-orders-$ORDER_ID-pay | |
| I'm not sure what you mean by "is not standard". First of all, we do not guarantee that this is an array, or even numbers. The idea is (for now) that this is the "text to show", and that if it has newlines, you should render it with newlines! These are 5 TOTP codes, and the idea is that the POS staff should match any single one of them. So I don't see why comma vs \n would be any better, or more "standard". My goal was to give it to you in exactly the format that you could just directly give to a rendering engine. Oh, and you should NOT render them in one long line, that's not the intended format here. The idea was to show one code per line on 3-5 lines. | |
| > Oh, and you should NOT render them in one long line, that's not the intended format here. The idea was to show one code per line on 3-5 lines. That's how the render engine is showing it, I will add a < pre > so the browser will render the \n > I'm not sure what you mean by "is not standard" For clarification: I meant a standard way of showing a list of numbers, people can understand a comma separated value and it will show exactly the same way everywhere. \n may not be rendered in the same way in html or in a cli using linux or windows. | |
| 2f8de9ea86cc1170b45e13fae6f0a66c7c4fd038 added | |
- Anonymous