|
|
| Reporter | Christian Grothoff | Assigned To | | |
|---|
| Priority | low | Severity | feature | Reproducibility | N/A |
|---|
| Status | confirmed | Resolution | open | |
|---|
| Platform | i7 | OS | Debian GNU/Linux | OS Version | squeeze |
|---|
| Product Version | 0.0.0 | |
|---|
|
|
| Summary | 0006917: cost calculations for annual fees by reducer are imperfect |
|---|
| Description | Right now, the code does not consider the possibility that the user may have already paid the 'annual_fee' at all or some providers for some of the time. Thus, the cost returned is strictly speaking an upper bound.
That said, this is only relevant for users that store multiple secrets and if annual fees are applicable. As we do not yet really support 'premium' accounts (with liabilities) in the reducer/UI, this is a very minor issue. |
|---|
| Additional Information | Fixing this will not only require us to change a synchronous transition to an asynchronous state transition, but we MAY also need to modify the REST API to obtain the current account expiration date from the service. Not sure, as we MAY also be able to find out the information using the existing API (need to check if the account expiration time is already returned). Cleanest way would likely be a HEAD request on the policy URL and then getting the info from the HTTP headers. |
|---|
| Tags | No tags attached. |
|---|
|
|
