-
Notifications
You must be signed in to change notification settings - Fork 47.2k
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
[ServerRenderer] Add option to send instructions as data attributes #25437
Changes from 11 commits
fe5caba
5e81c7d
575c581
62bf65f
7daf109
7920bb2
7e14a26
a3ee1a7
4cf4af1
ea37d85
df858fe
80a3b3d
f35926f
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -3,6 +3,7 @@ | |
* clients. Therefore, it should be fast and not have many external dependencies. | ||
* @flow | ||
*/ | ||
/* eslint-disable dot-notation */ | ||
|
||
// Imports are resolved statically by the closure compiler in release bundles | ||
// and by rollup in jest unit tests | ||
|
@@ -13,13 +14,91 @@ import { | |
completeSegment, | ||
} from './fizz-instruction-set/ReactDOMFizzInstructionSet'; | ||
|
||
// Intentionally does nothing. Implementation will be added in future PR. | ||
// eslint-disable-next-line no-unused-vars | ||
const observer = new MutationObserver(mutations => { | ||
// These are only called so I can check what the module output looks like. The | ||
// code is unreachable. | ||
clientRenderBoundary(); | ||
completeBoundaryWithStyles(); | ||
completeBoundary(); | ||
completeSegment(); | ||
}); | ||
if (!window.$RC) { | ||
// TODO: Eventually remove, we currently need to set these globals for | ||
// compatibility with ReactDOMFizzInstructionSet | ||
window.$RC = completeBoundary; | ||
window.$RM = new Map(); | ||
} | ||
|
||
if (document.readyState === 'loading') { | ||
if (document.body != null) { | ||
installFizzInstrObserver(document.body); | ||
} else { | ||
// body may not exist yet if the fizz runtime is sent in <head> | ||
// (e.g. as a preinit resource) | ||
const domBodyObserver = new MutationObserver(() => { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I feel like I am missing something but does this observer ever observe anything? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Ahh I can't believe I didn't call observe, thanks so much for catching this - definitely a problem. |
||
// We expect the body node to be stable once parsed / created | ||
if (document.body) { | ||
if (document.readyState === 'loading') { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Not sure the order of DOM parsing / changing readyState - this could totally be a redundant check Added just in case readyState gets set (experimented with inline scripts on my laptop's version of Chrome, but wary about other browser implementations) There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I don't know off the top of my head. seems safe enough to leave in |
||
installFizzInstrObserver(document.body); | ||
} | ||
handleExistingNodes(); | ||
domBodyObserver.disconnect(); | ||
} | ||
}); | ||
} | ||
} | ||
|
||
handleExistingNodes(); | ||
|
||
function handleExistingNodes() { | ||
const existingNodes = document.getElementsByTagName('template'); | ||
for (let i = 0; i < existingNodes.length; i++) { | ||
handleNode(existingNodes[i]); | ||
} | ||
} | ||
|
||
function installFizzInstrObserver(target /*: Node */) { | ||
const fizzInstrObserver = new MutationObserver(mutations => { | ||
for (let i = 0; i < mutations.length; i++) { | ||
const addedNodes = mutations[i].addedNodes; | ||
for (let j = 0; j < addedNodes.length; j++) { | ||
if (addedNodes.item(j).parentNode) { | ||
handleNode(addedNodes.item(j)); | ||
} | ||
} | ||
} | ||
}); | ||
// We assume that instruction data nodes are eventually appended to the | ||
// body, even if Fizz is streaming to a shell / subtree. | ||
fizzInstrObserver.observe(target, { | ||
childList: true, | ||
}); | ||
window.addEventListener('DOMContentLoaded', () => { | ||
fizzInstrObserver.disconnect(); | ||
}); | ||
} | ||
|
||
function handleNode(node_ /*: Node */) { | ||
// $FlowFixMe[incompatible-cast] | ||
if (node_.nodeType !== 1 || !(node_ /*: HTMLElement*/).dataset) { | ||
return; | ||
} | ||
// $FlowFixMe[incompatible-cast] | ||
const node = (node_ /*: HTMLElement*/); | ||
const dataset = node.dataset; | ||
if (dataset['rxi'] != null) { | ||
clientRenderBoundary( | ||
dataset['bid'], | ||
dataset['dgst'], | ||
dataset['msg'], | ||
dataset['stck'], | ||
); | ||
node.remove(); | ||
} else if (dataset['rri'] != null) { | ||
// Convert styles here, since its type is Array<Array<string>> | ||
completeBoundaryWithStyles( | ||
dataset['bid'], | ||
dataset['sid'], | ||
JSON.parse(dataset['sty']), | ||
); | ||
node.remove(); | ||
} else if (dataset['rci'] != null) { | ||
completeBoundary(dataset['bid'], dataset['sid']); | ||
node.remove(); | ||
} else if (dataset['rsi'] != null) { | ||
completeSegment(dataset['sid'], dataset['pid']); | ||
node.remove(); | ||
} | ||
} |
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.
Why expose this on the window? We shouldn't need to expose anything on the global when we're running a custom external runtime with its own closure.
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 currently access this variable through
window
here.We can add a compile-time variable (similar to
__DEV__
) to compile this access away when bundling the external runtime. There probably is a better solution I'm missing thoughThere 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.
Yeah I left a TODO for that when I set up the Closure compilation step. I tried setting it up so that the arguments get passed into the function ("dependency injection"), which worked, but Closure wasn't inlining it as well as it should in the inline runtime. I think it could be solved by running Rollup before running Closure, like we do for our main bundles.
I can look into improving that if you like @mofeiZ