Conversation
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.
a truly stunning work
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.
Is this really a significant metric?
# We first create a new Message, and then we check how long it took to send the message by comparing it to the current time | ||
m = client.create_message(payload.channel_id, "Pong!") | ||
time = Time.utc_now - payload.timestamp | ||
client.edit_message(m.channel_id, m.id, "Pong! Time taken: #{time.seconds}.#{time.milliseconds} seconds.") |
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.
Use a time format here
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.
I agree.
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.
Not possible for TIme Spans (I'll push other way/fix in a minute)
imo this could go inside the multicommand example, as it's not a very significant example |
@neko Or it could go with the current ping example ( |
Ping example is meant to be the first, simple, example: listen for x, respond with y. |
8998ef1
to
cd98f8c
Compare
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.
Squash these two
cd98f8c
to
eae32a7
Compare
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.
examples/ping_with_response_time.cr
eae32a7
to
a3d1b81
Compare
its k |
No description provided.