Closed riderx closed 1 year ago
/bounty 200
π $200 bounty created by riderx
π If you start working on this, comment
/attempt #37
to notify everyoneπ To claim this bounty, submit a pull request that includes the text
/claim #37
somewhere in its bodyπ Before proceeding, please make sure you can receive payouts in your country
π΅ Payment arrives in your account 2-5 days after the bounty is rewarded
π― You keep 100% of the bounty award
βΉοΈ If something is not clear ask before working on it, otherwise your chance to rework it is high
π¨βπ©βπ§βπ¦ Join the Discord to get help
π Thank you for contributing to Cap-go/capacitor-updater!
Attempt | Started (GMT+0) | Solution |
---|---|---|
π‘ @WcaleNieWolny | Aug 18, 2023, 11:01:04 AM | #276 |
Hi! I would like to work on this!
/attempt #37
@tachyonicbytes let go i will share with you more details then. I believe this task has to be done in https://github.com/Cap-go/capgo What need to be done:
Is the channel sufficient for collecting the test results? As I see it, the type A or B has to be associated with the client, in order to collect the test results. Theoretically, it may go down to two metadata points, a "is client part of A/B testing", and "A/B testing type". The latter may be enough though.
Since this has not been active for a long time I am attempting this
/attempt #37
Here are my changes so far:
I also would like to ask: How should we handle the %? How do I update this without causing a spam to the supabase? If I update this on every change this will generate A LOT of requests
You cannot have 1 bundle on multiple channels: (It will unlink the other channel if you attempt this, not sure how to handle when users attempts to set bundle on 2 AB channels at once)
Linking also works
Please let me know if that was what you was hoping for @riderx
@WcaleNieWolny just a debounce on the % will be good i believe ! Pretty cool, i just wonder how user will use this, like how they will measure they test
I would like to confirm:
if (!signedURL || signedURL.startsWith('http://') || !signedURL.startsWith('https://'))
Is this the intended behavior? I do not understand why HTTP without TLS would be disallowed to be honest
/claim #37
I cannot claim this, since the PR is in another repo
@WcaleNieWolny because on android itβs disabled by default, so if you try http you will have that to work only in iOS . So I made the plugin behave the same in both
Oh, okay in that case. I will just not commit my change and change this only for testing purposes
ππ @WcaleNieWolny has been awarded $200! ππ
Allow 50% to have one version and 50% to have other to see if that improve specific stat