luckyframework / luckyframework/breeze

Show timing on requests

Open
#33 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

  • #48 by @someone — closed without merging
Dominant language
Crystal
Stars
22
Forks
2
PR merge metrics
No merged PRs in 30d

Description

In the log, I can see

> ▸ Sent 200 OK (70.18ms)

but if I view that request in Breeze, I don't see that 70ms anywhere. It would be nice to know if I made a change, and all of a sudden that number was averaging 100ms, or I did something that made it go down.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing closed pull request #48, then trace how the log shows request duration and where the request is rendered in Breeze. Done means the request view displays the timing shown in the log so changes in duration can be compared.

Written by the indexing model from the issue text.

Assessment

Tech stack
crystal
Domain
observability
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.