enki/blap-android
1
0
Fork 0
Code Issues Pull Requests Actions 6 Packages Projects Releases 4 Wiki Activity

Avoid describing Pro-build specifics in the recovery setup entry point doc

Browse Source 
Genericise the SecureBackupSetupEntryPoint KDoc so the public repo no longer
spells out the enterprise custom recovery passphrase behaviour.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
Jenna Vassar
2026-06-09 12:15:21 -07:00
parent b8daada2a3
commit 2a66df7b8a
1 changed files with 2 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
features/securebackup/api/src/main/kotlin/io/element/android/features/securebackup/api/SecureBackupSetupEntryPoint.kt
+2 -3
View File
@@ -15,9 +15,8 @@ import io.element.android.libraries.architecture.NodeInputs
/**
* Entry point for the recovery-key setup screen.
*
* The default (FOSS) implementation builds the standard auto-generated-key setup node. Enterprise
* builds replace this binding to vend a richer setup node (e.g. a homeserver-advertised custom
* recovery passphrase) while falling back to the standard node when no custom spec applies.
* The default implementation builds the standard auto-generated-key setup node. The binding can be
* replaced to provide an alternative setup node.
*/
interface SecureBackupSetupEntryPoint : FeatureEntryPoint {
data class Inputs(val isChangeRecoveryKeyUserStory: Boolean) : NodeInputs