-
Notifications
You must be signed in to change notification settings - Fork 243
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
Fix: don't auto import experimental bento components #1234
Conversation
e6c04c3
to
bd730b5
Compare
Use the bento component info published here https://amp.dev/static/bento-components.json to determine which version of a component to auto import. Fixes #1221
let bentoComponentInfo = await config.cache.get('bento-component-info'); | ||
if (!bentoComponentInfo) { | ||
bentoComponentInfo = await fetchBentoComponentInfo_(config); | ||
config.cache.set('bento-component-info', bentoComponentInfo); |
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.
do we have any concern about a cache error?
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.
Good point, made this handle errors with a single warning
bd730b5
to
3f6febe
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.
one question, otherwise lgtm
* Don't auto import experimental bento components Use the bento component info published here https://amp.dev/static/bento-components.json to determine which version of a component to auto import. Fixes #1221 * handle cache failures
Don't auto import experimental bento components. Pull in latest component prod version from the amphtml repository. Fixes #1221
Fixes #1221