-
Notifications
You must be signed in to change notification settings - Fork 20
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 new platform user VC: daren market #2903
Conversation
cc23492
to
f2050e9
Compare
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.
Thanks!
Apart from this PR itself, we need to double-check:
- the API keys are listed and imported in the deployment cc @m1iktea
- if the enum change is a breaking change cc @jonalvarezz
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 don't need to change it - actually we should remove all data provider envs for bc-worker
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.
sure. Let's do it in another PR to remove all unrelated entries.
P-935 : remove env entries
MagicCraftStaking, | ||
#[codec(index = 2)] | ||
DarenMarket, |
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 assume this will be a breaking change for the SDK? @jonalvarezz
|
||
let mut config = DataProviderConfig::new().unwrap(); | ||
config.set_karat_dao_api_url(url).unwrap(); |
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.
Hmm so we never set magic_craft
? How did it work before? 🤔
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.
Previously magic_craft was not tested.
|address| match client.user_verification(address.to_string(), true) { | ||
Ok(response) => | ||
if response.created { | ||
result = true; | ||
Ok(LoopControls::Break) | ||
} else { | ||
Ok(LoopControls::Continue) | ||
}, | ||
Err(err) => Err(err.into_error_detail()), | ||
}, | ||
AbortStrategy::ContinueUntilEnd::<fn(&_) -> bool>, |
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.
Hmm fail_fast
is true here but we are using AbortStrategy::ContinueUntilEnd
, it seems a bit confusing.
Or maybe they shouldn't be used together?
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.
fail_fast
is used for querying data from data provider. AbortStrategy::ContinueUntilEnd
is for the loop through all addresses. So they are not conflicting with each other.
@Kailai-Wang regarding the API KEY, our partner has not yet ready to provide it. We are still waiting for them to test it out. CC: @m1iktea |
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.
Approved on condition that negative case i.e. false value VC is also tested
Confirmed with partner Daren. They will provide public API. So there will be no API KEY. |
_enum: ["KaratDaoUser", "MagicCraftStakingUser"], | ||
_enum: ["KaratDao", "MagicCraftStaking", "DarenMarket"], | ||
}, |
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 will need to update client-api, but not a breaking change for client-sdk nor clients in general.
As title, add new VC support.
Related changes: litentry/vc-jsonschema#42
Testing Evidences
Please attach any relevant evidences if applicable