-
Notifications
You must be signed in to change notification settings - Fork 184
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
Handle Null and Promise.resolve(null) in renderMetaTags + renderLinkTags #805
Handle Null and Promise.resolve(null) in renderMetaTags + renderLinkTags #805
Conversation
…LinkTags(). Added a test harness for renderMiddleware to test this bug fix in the future.
it("don't render meta tags", (finishTest) => { | ||
_testFunctions.renderMetaTags(page, mockSocket) | ||
.then(() => { | ||
expect(mockSocket.toString()).toMatch(''); |
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.
Whoa, cool!
LGTM 👍 Thanks @drewpc! |
I forgot to add a 'normal' values check! I'll do that now. |
lgtm |
# Conflicts: # packages/react-server/package.json
No changes since I submitted the PR. I saw that there were merge conflicts based on the latest dependency changes in the master branch and resolved the conflicts. |
Thanks for jumping on that. |
Fixed handling of
null
andPromise.resolve(null)
forrenderMetaTags
andrenderLinkTags
. Added a test harness forrenderMiddleware
which was used to recreate the problem and ensure successful resolution. Corresponds to issue #789