-
Notifications
You must be signed in to change notification settings - Fork 628
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
New: Add manifest-scoped-urls #2328
Conversation
dae489d
to
fcc0b12
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.
Nice job, a few comments and requests for more tests but this is looking good.
@@ -0,0 +1,84 @@ | |||
import { test } from '@hint/utils'; |
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 think we should also test the local connector but I'm not sure how to check that things are correct because paths can be anything locally 🤔
@antross do you have any suggestion?
@shivangg also need to add |
@molant Added location information to reports as well as tests. |
@shivangg looks like tests are failing. Can you please take a look at the output in Azure Pipelines |
381d149
to
03b6198
Compare
@molant Was failing a test case. Should pass now (Linux and windows). |
Checks that start_url is accessible and in scope. Checks either name or short_name is specified Resolves webhintio#2058
03b6198
to
807e464
Compare
@shivangg looks like Linux failed. I'm re-running it see if there's any change. |
And now it's passing 🎉 |
@antross we have the pending question of local connector. Maybe we should change the scope of this one to be web only for now? |
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.
Looking good overall. Just a few pieces we still need to sort out.
97ec5c4
to
4c5499d
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.
Very minor things, I think that's all about strings. It's looking really good!
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.
Looks like a few of the tests are failing in CI:
- ✖ [chrome] Manifest property start_url is relative and inaccessible. No reports match "Specified 'start_url' is not accessible. Status code: '404'." or its location ({"column":21,"line":2}).
- ✖ [chrome] No start_url property specified in Manifest file No reports match "Property 'start_url' not found in manifest file." or its location ({"column":-1,"line":-1}).
- ✖ [chrome] Manifest property start_url has preceding
/
and scoped but inaccessible No reports match "Specified 'start_url' is not accessible. Status code: '404'." or its location ({"column":21,"line":2}).
Otherwise just some minor cleanup suggestions. Once the tests are fixed this should be ready to merge.
As per code review suggestions Co-Authored-By: shivangg <shivangg@users.noreply.github.com>
62357cf
to
d8ce622
Compare
All tests passing now. 😄 |
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.
Looks good to me. Nice work @shivangg! 🎉
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
@molant It passes the thresholds in the Azure pipelines. |
Pull request checklist
Make sure you:
For non-trivial changes, please make sure you also:
Short description of the change(s)
Fixes #2058