Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ui: (bonds) improve penalty compensation UX #3187

Open
norwnd opened this issue Feb 16, 2025 · 1 comment
Open

ui: (bonds) improve penalty compensation UX #3187

norwnd opened this issue Feb 16, 2025 · 1 comment

Comments

@norwnd
Copy link
Contributor

norwnd commented Feb 16, 2025

First, I think bond Auto renew toggle should be on by default (simply because this targets the widest user-base, the minority should do the work - not the majority), but regardless

I think it would be better for Penalties Comps to be a toggle (and not a number) that is also on whenever Auto renew toggle is on with 1 exception being:

  • when user hits penalty threshold often (I would say if he hits it 3 times consecutively) he should be notified about it, probably to the point of turning Penalties Comps toggle to off so that user will have to re-enable it manually in settings (acknowledging he knows what's happening)

The reason for Penalties Comps to be a toggle is so it is managed automatically without user knowing about it until it's clear he should look into it,

but also here is a list of issues with Penalties Comps being a number (at least the way it's currently implemented):

  • it's not entirely clear what number to input (or what would happen if you enter a value lower/higher than what Penalties show)
  • it doesn't persist the value entered always resetting it to 0 (I set it to 1, and now it's 0), so I have no way to tell whether I'm compensating for penalties or not (unless maybe I'm trying to subtract target-actual tier, but the values might not add up when the bond is being posted I guess too)
  • and the input field itself is kind of janky / hard to work with (I guess you have not only input number in there but also hit Enter?)
@JoeGruffins
Copy link
Member

JoeGruffins commented Feb 19, 2025

it doesn't persist the value entered always resetting it to 0

This was a bug should be fixed in #3188

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants