Skip to content
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

Fixes property lookup on null if promobarContent node doesn't exist #1

Merged
merged 1 commit into from
Oct 4, 2016

Conversation

maxrolon
Copy link
Contributor

@maxrolon maxrolon commented Oct 4, 2016

No description provided.

Copy link
Contributor

@estrattonbailey estrattonbailey left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, makes sense. Keep in mind that even things like a className change or something would invalidate the cache in this case. Probably not a huge deal or common scenario.

The design here was intended to force a user to provide content to the cache instead of relying on assumption about the content in the event that assumption could be wrong. This seems to be a pretty safe assumption though.

Idk why you're not on this repo, I'll add you.

@maxrolon maxrolon merged commit e28bb67 into master Oct 4, 2016
@wturnerharris wturnerharris deleted the ReferenceError-fix branch October 4, 2016 18:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants