This is a bit of an issue, because we sometimes use the Weekly Call room for other meetings. Not sure what the best solution is. Maybe just something generic like "Team/Community Call".
This is a bit of an issue, because we sometimes use the Weekly Call room for other meetings. Not sure what the best solution is. Maybe just something generic like "Team/Community Call".
but we also need to test that four our kosmos call we get the correct participants.
Not sure what you mean by "test". The participants will only ever be whatever their current Zoom display name is. Hence, the integration needs to ignore non-existing ones I believe. It will be a normal situation to not have all participants use a name, or have the right in their profile (or have a profile at all).
Edit: I also forgot to comment on the code: we established that re-connects add the same user multiple times to the array of the Zoom call object, so we need to use unique values in order to prevent multiple contributions from being created.
> but we also need to test that four our kosmos call we get the correct participants.
Not sure what you mean by "test". The participants will only ever be whatever their current Zoom display name is. Hence, the integration needs to ignore non-existing ones I believe. It will be a normal situation to not have all participants use a name, or have the right in their profile (or have a profile at all).
Edit: I also forgot to comment on the code: we established that re-connects add the same user multiple times to the array of the Zoom call object, so we need to use unique values in order to prevent multiple contributions from being created.
I could not test the full integration yet, because I can not get data from the past meeting participants endpoint.
that's for paid plans only and I had issues with the JWT. That's what we need to pair on using the kosmos zoom account.
I could not test the full integration yet, because I can not get data from the [past meeting participants](https://marketplace.zoom.us/docs/api-reference/zoom-api/meetings/pastmeetingparticipants) endpoint.
that's for paid plans only and I had issues with the JWT. That's what we need to pair on using the kosmos zoom account.
What's the case of tx being falsey (maybe makes sense to explain that in a comment)? Btw, I think we can replace the then with saving the result in a variable from the await, like so:
What's the case of tx being falsey (maybe makes sense to explain that in a comment)? Btw, I think we can replace the `then` with saving the result in a variable from the `await`, like so:
```js
const tx = await createContributionFor(displayName, meetingDetails);
if (tx) log(foo);
```
bumi
(Migrated from github.com)
reviewed 2020-04-16 15:15:30 +00:00
if the contributor is not found then there is no tx.
not sure how to best handle this one: https://github.com/67P/hubot-kredits/pull/53/files#diff-74e18db4da1da4461c9ccb134c582a3eR26
if the contributor is not found then there is no tx.
raucao
(Migrated from github.com)
reviewed 2020-04-16 15:17:05 +00:00
Dang, it slipped through my review that the documentation for this feature was missing in the README. (If it's not documented, it's not a feature.)
Edit: created #57 for it.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
closes #34
LGTM 👍
Added some code suggestions.
This is a bit of an issue, because we sometimes use the Weekly Call room for other meetings. Not sure what the best solution is. Maybe just something generic like "Team/Community Call".
By the way, I just checked Rinkeby kredits, and none of our profiles have Zoom display names stored yet...
Yes, we need to collect all the zoom names.
but we also need to test that four our kosmos call we get the correct participants.
Not sure what you mean by "test". The participants will only ever be whatever their current Zoom display name is. Hence, the integration needs to ignore non-existing ones I believe. It will be a normal situation to not have all participants use a name, or have the right in their profile (or have a profile at all).
Edit: I also forgot to comment on the code: we established that re-connects add the same user multiple times to the array of the Zoom call object, so we need to use unique values in order to prevent multiple contributions from being created.
I could not test the full integration yet, because I can not get data from the past meeting participants endpoint.
that's for paid plans only and I had issues with the JWT. That's what we need to pair on using the kosmos zoom account.
Ah, OK. Got it.
@@ -0,0 +16,4 @@const walletTransactionCount = await kredits.provider.getTransactionCount(kredits.signer.address);let nonce = walletTransactionCount;async function createContributionFor (displayName, meeting) {I think we should not do this. It will be a normal thing in a public call that not everyone is a contributor with a profile.
@@ -0,0 +72,4 @@if (meetingDetails.duration < 15 || meetingDetails.participants_count < 3) {robot.logger.info(`[hubot-kredits] Ignoring zoom call ${data.uuid} (duration: ${meetingDetails.duration}, participants_count: ${meetingDetails.participants_count})`);return;What's the case of tx being falsey (maybe makes sense to explain that in a comment)? Btw, I think we can replace the
thenwith saving the result in a variable from theawait, like so:@@ -0,0 +72,4 @@if (meetingDetails.duration < 15 || meetingDetails.participants_count < 3) {robot.logger.info(`[hubot-kredits] Ignoring zoom call ${data.uuid} (duration: ${meetingDetails.duration}, participants_count: ${meetingDetails.participants_count})`);return;not sure how to best handle this one: https://github.com/67P/hubot-kredits/pull/53/files#diff-74e18db4da1da4461c9ccb134c582a3eR26
if the contributor is not found then there is no tx.
@@ -0,0 +72,4 @@if (meetingDetails.duration < 15 || meetingDetails.participants_count < 3) {robot.logger.info(`[hubot-kredits] Ignoring zoom call ${data.uuid} (duration: ${meetingDetails.duration}, participants_count: ${meetingDetails.participants_count})`);return;Wait, if the contributor is not found, then the promise wouldn't resolve, would it? In that case it should reject.
Dang, it slipped through my review that the documentation for this feature was missing in the README. (If it's not documented, it's not a feature.)
Edit: created #57 for it.