Add missed react_component_hash functionality#960
Conversation
|
Reviewed 11 of 11 files at r1. spec/dummy/package.json, line 10 at r1 (raw file):
why did this change? Comments from Reviewable |
|
I'd like to get the rest of my PRs reviewed, fixed, approved, and merged before release. Review status: all files reviewed at latest revision, 1 unresolved discussion, some commit checks failed. spec/dummy/package.json, line 10 at r1 (raw file): Previously, justin808 (Justin Gordon) wrote…
Because with yarn v1, the old syntax sends the Comments from Reviewable |
|
Why no CHANGELOG.md and doc change, @Judahmeek? Review status: all files reviewed at latest revision, all discussions resolved, some commit checks failed. Comments from Reviewable |
3af19dd to
7840494
Compare
|
My bad, @justin808. For some reason, I was thinking that CHANGELOG updates were only required on release. I forgot about the unreleased section. That said, I don't think any doc changes are required since this PR simply ensured that Btw, #957 is also ready for re-review. Review status: 11 of 12 files reviewed at latest revision, all discussions resolved, some commit checks failed. Comments from Reviewable |
7840494 to
da497c1
Compare
|
Review status: 11 of 12 files reviewed at latest revision, all discussions resolved, some commit checks failed. Comments from Reviewable |
|
Reviewed 1 of 1 files at r2. Comments from Reviewable |
When I created #951, I forgot to add the useful functionality from #950 that would ensure that
react_component_hashworked correctly. When there is a prerendering error,react_component_hashshould return the result combined with the console logs as a hash even though every prerendering error is returned fromExecas a String. Right now, if a prerendering error occurs,react_component_hashthrows its "Expected a Hash" errorExpected Behavior:

Current Behavior:

This change is