-
Notifications
You must be signed in to change notification settings - Fork 10
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
let a client accept external client_args #39
Conversation
@carlhoerberg wdyt, ready or not? |
This record introduces two new client properties, product_version and platform_version which are supposed to replace version
940b359
to
e5a820e
Compare
5288b82
to
ef6cca8
Compare
src/amqp-client/connection.cr
Outdated
platform: "Crystal", | ||
version: AMQP::Client::VERSION, | ||
capabilities: Arguments.new({ | ||
connection_name: name || connection_information.name, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can the name assigment be done earlier, so that this method don't have to receive both arguments, just the ConnectionInformation with name set?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Put it before right before start()
now
@kickster97 make to always squash PRs, don't merge the whole PR commit history with main. Now we have "format", "fix" etc in the main commit history. |
Yes ofc! my mistake |
This PR lets amqp-client be able to take in external client arguments so it can present more accurate client information for connections.
In the image below we see it states amqp-client instead of LavinMQ.
If it was RabbitMQ, it would state RabbitMQ so assuming that is the standard