-
Notifications
You must be signed in to change notification settings - Fork 88
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
Add support to search for web features in searchcache [Part 3/4] #3665
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.
Note to myself: Need to finish reviews for polling and cache logic
32da8d1
to
d8bd9d3
Compare
9d67f32
to
42c9201
Compare
The service will now interpret a query that takes the form of feature:<web-feature-key> Similarly to the searchcacheMetadataFetcher, there is now a searchcacheWebFeaturesManifestFetcher
Co-authored-by: Kyle Ju <kyleju@google.com>
583b4dd
to
7d893db
Compare
This is ready for another review @KyleJu |
Chatted offline. The downloading Manifest bit can be moved to the shared/ directory |
Since most of the logic has been moved into shared, I was able to unexport a lot of things I thought I would need
Note to reviewers: Moving all the Github logic to shared allowed me to:
|
@KyleJu This is ready for another round |
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.
LGTM. Thanks for addressing all the comments!
Co-authored-by: Kyle Ju <kyleju@google.com>
When testing in my own repo, the Name field worked. But now that the wpt releases are automated, the label is the correct field
@KyleJu I added one more commit. I think it should be fine but don't want to assume. Let me know what you think of that commit |
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.
LGTM again
The service will now interpret a query that takes the form of feature:
Similarly to the searchcacheMetadataFetcher, there is now a searchcacheWebFeaturesManifestFetcher