You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Transport references are generated randomly, which results in generated files being different every time they are built even if the actual DOM does not have any changes. A better option would be to somehow make the transport references deterministic while maintaining their uniqueness across the DOM tree.
The main difficulty of that is situations where a compiled HTML snippet is used across multiple HTML files. In that situation the transport references within the re-used snippet should not collide with transport references within the host HTML.
Potential solutions:
default to a super-deterministic transport ref generator like a counter, then allow for namespacing, either via the StaticRenderer, via Context object, etc. the problem is that this is not a fix, but rather opening up API surface and allowing users to implement context-based fixes (it is notable that this is also what JSS does and it doesn't look that bad over there).
use document.currentScript to avoid needing a transport reference to begin with. the problem is that then we would be unable to support IE anymore.
The original discussion on this matter happened in this issue.
The text was updated successfully, but these errors were encountered:
I personally would wait a year until IE usage dies off, and then switch to document.currentScript. We could potentially even decide to drop IE support sooner as well.
Transport references are generated randomly, which results in generated files being different every time they are built even if the actual DOM does not have any changes. A better option would be to somehow make the transport references deterministic while maintaining their uniqueness across the DOM tree.
The main difficulty of that is situations where a compiled HTML snippet is used across multiple HTML files. In that situation the transport references within the re-used snippet should not collide with transport references within the host HTML.
Potential solutions:
StaticRenderer
, viaContext
object, etc. the problem is that this is not a fix, but rather opening up API surface and allowing users to implement context-based fixes (it is notable that this is also what JSS does and it doesn't look that bad over there).document.currentScript
to avoid needing a transport reference to begin with. the problem is that then we would be unable to support IE anymore.The original discussion on this matter happened in this issue.
The text was updated successfully, but these errors were encountered: