You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently don't have a LightHouse CI workflow which will check for Performance, Accessibility, Best practices, SEO, PWA for each PR and we manually need to go to the deployment and check it.
Desired Behavior
We should have a bot which will comment the LightHouse report for our convenience in each PR.
@aakankshabhende, I think this is generally a positive thing, particularly when it comes to the Catalog pages. With this said, of the effort that we're going to incorporating lighthouse in this repo, there are a couple of higher priority areas in need of help where your efforts will be both better supported and more impactful.
The meshery.io/catalog offers no way to filter catalog content by content type: design pattern versus wasm filter versus meshery model. @vishalvivekm has been unable to implement this. Perhaps, you can.
The list of relationships in Meshery UI's Settings page is missing details that users need in order to find that UI helpful. I have sent details in Slack on this subject.
Current Behavior
We currently don't have a LightHouse CI workflow which will check for Performance, Accessibility, Best practices, SEO, PWA for each PR and we manually need to go to the deployment and check it.
Desired Behavior
We should have a bot which will comment the LightHouse report for our convenience in each PR.
Workflow action: https://github.com/treosh/lighthouse-ci-action
The text was updated successfully, but these errors were encountered: