Closed waddaboo closed 3 weeks ago
The latest updates on your projects. Learn more about Vercel for Git ↗︎
Name | Status | Preview | Comments | Updated (UTC) |
---|---|---|---|---|
bandada-docs | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Oct 31, 2024 8:57am |
bandada-website | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Oct 31, 2024 8:57am |
Since the associated groups will only be used for the invite codes, we should make sure that people can't add members to those off-chain groups. What do you think?
If you try to use an invite code with the client app, you can see that the new member is added to the associated off-chain group.
Right, so the associated group will be used solely to generate invite codes and will not store any other information. I'll update it.
What about checking here if there is no other group with the same name when creating a group? This way, future issues can be avoided.
For this unique name check, do you want it to be unique for the whole database or just unique to admin?
For this unique name check, do you want it to be unique for the whole database or just unique to admin?
Unique per admin.
I have implemented the requested changes and new features. Feel free to continue your review. Thanks!
Description
This PR introduces multiple new features to api, dashboard, and api-sdk.
New features included:
Related Issue
Does this introduce a breaking change?
Other information
Associated off-chain group flow:
type="on-chain" && name="groupId"
.getGroupByName(name, type)
.getAssociatedGroups(name)
.