-
-
Notifications
You must be signed in to change notification settings - Fork 659
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 multi-message produce feature #791
Conversation
Hi :)
or {"key": "key1","value": {"id": "123"}}
{"key": "key2","value": {"id": "456"}} A simple checkbox for multiple message, and we display a notice about the format needed ? What do you think about that ? |
Good idea! The checkbox combined with a text field for the separator would do the job. Let me check and get back to you :) |
@xpr3sso : does this one can be review ? |
Hi @tchiotludo, |
thanks @xpr3sso works great 👍 |
Co-authored-by: xpr3sso <xpr3sso@noreply.org>
Hi @tchiotludo,
This feature allows the user to input multiple records as key-value pairs at once as one-liners like:
or
This can help when dealing with larger sets of generated data - there is a limit for the request size, though :D
Multiple key-value separators can be chosen from, to support various naming conventions people might have.
Looks like this on the front end:
The "Key" field gets disabled when "Multiple messages" is selected, the multi-message fields for standard "Single message" producing. Placeholders for both modes are added to give some guidance.
What do you say? Could this be useful in general?