This is a bugfix imo:
If you have 2 server admins, where only Admin1 has access to a specific app and Admin2 goes to edit the policies, the mapping would be overwritten to "None" .
This PR exposes all apps on all stores to this mapping dropdown irrespective of user. I think it makes sense to leak this minor data here to server admins.
* Fix "Do not propose lightning payment if value of the invoice is above..."
* Fix "Do not propose lightning payment if value of the invoice is above..." take care of the GAP edge case where OnChainMinValue > LightningMaxValue
* Fix "Do not propose on chain payment if the value of the invoice is below..." and take care of the GAP edge case
* Add test to cover all case and fix small issue
* Simplified version, with less validation
* added View App button to POS settings
updated POS settings form group buttons to match Crowdfund settings from group buttons, addressing #854
* added View App button to POS settings #947
Fixed "Save Settings" Redirect
* Start adding more options to Custom Amount Pay button
This allows you to simplify the custom amount pay button to remove the big + & - buttons along with set a min, max and step amounts. There's also an option to fit the button next to the input amount to have it more condensed(not finished)
* make fit button inline work nicely
* make currency dropdown more obvious
* fix space
With value 60 what would often happen is that invoice ends up being declared invalid, and then payment arrives later when system is not monitoring. After lots of production testing we decided to increase this value by default so that new users don't need to manually reassign invoices from `invalid` status, especially if they use third party plugin like wooCommerce.
