| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
There was a problem hiding this comment.
@rytisder Thank you for the pull request!
This looks great. I have a few bits of small feedback, most importantly it would be great to make the threshold value filterable so that external code such as plugins can change it.
Sorry, something went wrong.
|
@rytisder Thanks for fixing it so quickly. |
Sorry, something went wrong.
There was a problem hiding this comment.
@rytisder Thank for the updates, looks great! I just left a few more comments, almost all of them small details. Functionally this is already good, but it would be great if you could address the remaining feedback.
FYI no need to force-push, we typically just work with full commit history. So you can just add commits as you go.
Sorry, something went wrong.
|
Hello @rytisder thanks for the PR, it really makes this site health check more self-explanatory and complete :) |
Sorry, something went wrong.
|
@rytisder I will add some additional feedback on the PR, Below is the description for changes that I request.
@felixarntz In WordPress site health report it doesn't use a number column to identify its column number in any of their site health report in the info tab( WordPress, Directories and Sizes, Server, etc..) so for consistency do we need to remove it? |
Sorry, something went wrong.
|
@mukeshpanchal27 Thank you, great additional points!
Agreed, let's remove the first # column. @rytisder Would be great if you could follow up on the additional feedback above! :) |
Sorry, something went wrong.
|
@felixarntz, all suggestions mentioned above are pushed! 🙂 |
Sorry, something went wrong.
|
This isn't ready yet due to the outstanding iterations requested, so I'll remove the 1.3.0 milestone from here. Once this gets picked up and continued towards merge, we can add a milestone again. @rytisder Will you be able to continue on the iterations requested above? If not, would you be open to another contributor taking over and continuing your work? |
Sorry, something went wrong.
|
Reminder:
|
Sorry, something went wrong.
There was a problem hiding this comment.
@rytisder Thanks for the update. PR looks good now. Can you please address feedback and merge the latest changes from trunk into your branch.
Sorry, something went wrong.
|
Set milestone to 1.5. Feel free to update change it if this is not ready. |
Sorry, something went wrong.
There was a problem hiding this comment.
@mukeshpanchal27 Since the remaining 2 tweaks from https://github.com/WordPress/performance/pull/353/files#r967984960 and #353 (review) are so tiny, let's merge this and then addresse those things in a follow up PR right after, if you're okay with that.
Sorry, something went wrong.
There was a problem hiding this comment.
Thank you very much, @rytisder! For the remaining work on this PR, we will create a separate PR.
Sorry, something went wrong.
|
@tillkruss Can you please review so we can merge this and add new follow-up PR to address remaining points.
|
Sorry, something went wrong.
Looks like we can actually edit the branch here directly. In that case, we could also adjust it directly in here. But either way works, would be great if you could complete the work here. 🙌 |
Sorry, something went wrong.
Co-authored-by: Peter Wilson <519727+peterwilsoncc@users.noreply.github.com>
| Back | FazBrowse Home | New Git URL |
Summary
Example:
Fixes #350
Relevant technical choices
Checklist