Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Make "withdrawMultiple" query the recipient for each stream #774

Closed
PaulRBerg opened this issue Dec 29, 2023 · 0 comments
Closed

Make "withdrawMultiple" query the recipient for each stream #774

PaulRBerg opened this issue Dec 29, 2023 · 0 comments
Assignees
@smol-ninja
Labels
effort: medium Default level of effort. priority: 1 This is important. It should be dealt with shortly. type: feature New feature or request. work: complicated Sense-analyze-respond. The relationship between cause and effect requires analysis or expertise.

Comments

@PaulRBerg
Copy link
Member

As discussed in #773, the goal is to refactor the withdrawMultiple function not to have a to parameter anymore, and query the recipient for each stream provided in the streamIds array.
@PaulRBerg PaulRBerg added this to the V2.2 milestone Dec 29, 2023
@PaulRBerg PaulRBerg moved this to 📋 Not Started in Lockup 1.2.0 Dec 31, 2023
@PaulRBerg PaulRBerg added type: feature New feature or request. priority: 1 This is important. It should be dealt with shortly. work: complicated Sense-analyze-respond. The relationship between cause and effect requires analysis or expertise. effort: medium Default level of effort. and removed priority1 labels Jan 1, 2024
@PaulRBerg PaulRBerg changed the title Refactor "withdrawMultiple" to query the recipient for each stream Make "withdrawMultiple" query the recipient for each stream Jan 1, 2024
@smol-ninja smol-ninja self-assigned this Jan 4, 2024
@smol-ninja smol-ninja moved this from 📋 Not Started to 🏗 In progress in Lockup 1.2.0 Jan 4, 2024
@PaulRBerg PaulRBerg removed this from the V2.2 milestone Jan 4, 2024
@smol-ninja smol-ninja mentioned this issue Jan 8, 2024
Merged
@smol-ninja smol-ninja moved this from 🏗 In progress to 👀 In review in Lockup 1.2.0 Jan 8, 2024
@smol-ninja smol-ninja moved this from 👀 In review to ✅ Done in Lockup 1.2.0 Jan 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@smol-ninja smol-ninja

Labels
effort: medium Default level of effort. priority: 1 This is important. It should be dealt with shortly. type: feature New feature or request. work: complicated Sense-analyze-respond. The relationship between cause and effect requires analysis or expertise.
Projects
No open projects
Lockup 1.2.0
Status: ✅ Done
Milestone
No milestone
Development

No branches or pull requests
2 participants
@smol-ninja @PaulRBerg