-
Notifications
You must be signed in to change notification settings - Fork 662
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
Link Gate to determine link launch/attest behaviour #9956
base: master
Are you sure you want to change the base?
Conversation
Diffuse output:
APK
DEX
|
39b6a68
to
7ef4623
Compare
internal class DefaultLinkGate @Inject constructor( | ||
private val configuration: LinkConfiguration | ||
) : LinkGate { | ||
override val useNativeLink: Boolean |
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.
what's the advantage of keeping track of useNativeLink
separately from useAttestationEndpoints
if useNativeLink's value is equal to useAttestationEndpoints value?
ie is "native" link as opposed to "native + attest" going to exist in production? And if not, do we need to test it now?
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.
Native link without attestation will be the default in test-mode (there's no need to attest in this scenario). Since useAttestationEndpoints
could be false in test mode, we'll use useNativeLink
for the LinkActivityContract
. This PR doesn't reflect the test mode logic. I'll push an update.
) : LinkGate { | ||
override val useNativeLink: Boolean | ||
get() { | ||
if (FeatureFlags.nativeLinkEnabled.isEnabled) return true |
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 find it a bit confusing that we are only using the value of the feature flag if it is true
-- wdyt of renaming the flags to something like "forceNativeLinkEnabled" and "forceUseAttestationEndpoints"? Or just using the feature flag values directly.
I think either solution would work bc my main concern here is that I'll be frustrated if I set native link to off in the playground and then see native link anyways (bc config.useAttestation... is true e.g.)
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 just updated the logic, we shouldn't run into the scenario where config.useAttestation
overrides the FeatureFlag anymore
Summary
Link Gate to determine whether to use native link and attestation endpoints. This will be used in
Motivation
Testing
Screenshots
Screen.Recording.2025-01-22.at.2.11.01.PM.mov
Changelog