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
Release 0.4.0 #57
base: master
Are you sure you want to change the base?
Release 0.4.0 #57
Conversation
Regarding this bit... Lines 235 to 241 in ddd6d50
First of all, if this expression is running, don't we already know that the key didn't match, and thus the DOM node must be new? Secondly, it looks like My suspicioun is that Am I wrong?? |
Not true.
|
Oh man, unpacking this code is really tricky... I wish like hell there was a tool that would automate these spooky compression patterns so no one would need to write code like this. 😐 Anyway, thanks for the explanation. 🙂 |
Oh, one thought about keyed updates: I noticed you use the user-supplied key and then fall back to a generated key, e.g.:
In my own experiments, the element type is always part of the key - something like:
Otherwise, if we were to diff between, say, |
Any reason this got stranded here? I think the only issue was the element-type missing from the key? Other than that, it looks good to go? |
This is the preview of the 0.4.0 release
Changelog
k
property that can be used for hinting the reconciliation keybrotli
instead ofgzip
to maintain the 512 byte contractual limit