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.

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

Topic Subscribe #385

Open
NemanjaLugi opened this issue Apr 7, 2023 · 0 comments
Open

Topic Subscribe #385

NemanjaLugi opened this issue Apr 7, 2023 · 0 comments

Comments

@NemanjaLugi
Copy link

Hi!

Is there any special reason why the attributes parameter for subscribe method is Map<String, String>? Why is not Map<String, dynamic>?
It makes more sense because we can send the list of strings, bool, or something else through the attributes. For example, we need to send list of strings, but we can't do that with current implementations.

{​​​​​
    "ids": [
        "id1",
        "id2",
        "id3",
    ]
}​​​​​
Future<SubscribeResponse> subscribe({  
 required String protocol,
 required String topicArn,
 Map<String, String>? attributes,
 String? endpoint,
 bool? returnSubscriptionArn, 
 })
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant