-
Notifications
You must be signed in to change notification settings - Fork 7
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
Add numDaysAfterRedactingTradeData #191
Add numDaysAfterRedactingTradeData #191
Conversation
…_AFTER_REDACTING_TRADE_DATA - [401fc11] fix compilation error of android node - [2c231f5] remove unused files - [75f9c1a] Add numDaysAfterRedactingTradeData to be in sync with bisq-network/bisq2#3134
f408fb3
to
d4af3e1
Compare
@HenrikJannsen I connected the components with the value coming from the network (node and clients), and made it available for the general settings to display (that's hidden at the moment @nostrbuddha is working on it). Could you please review and let me know if there is a specific application/validation we need to do with that network number? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it would be better to fully implement it (incl. UI element and API part).
private val _numDaysAfterRedactingTradeData: MutableStateFlow<Int> = MutableStateFlow(90) | ||
override val numDaysAfterRedactingTradeData: StateFlow<Int> get() = _numDaysAfterRedactingTradeData | ||
override suspend fun setNumDaysAfterRedactingTradeData(days: Int) { | ||
// Not applicable for xClients |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should implement the API call as with other properties
@HenrikJannsen just checked, this is the UI you are referring to: I need the settings stuff for that and buddha is working on it, I'll merge this PR and create an issue to do the UI and allow edit (API impl) |
See also the controller in Bisq 2 for the validation of the min/max values. |
follow up of -> #174