Update dependency @welldone-software/why-did-you-render to v6 #47
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
4.0.6->6.2.3Release Notes
welldone-software/why-did-you-render
v6.2.3Compare Source
v6.2.2Compare Source
v6.2.1Compare Source
v6.2.0Compare Source
v6.1.4Compare Source
jsx-runtimetypes (Thank you @hrazmsft)v6.1.3Compare Source
v6.1.2Compare Source
defaultPropsbeing lost on components patched by wdyr. Thank you @joeyparis!! https://github.com/welldone-software/why-did-you-render/pull/194v6.1.1Compare Source
v6.1.0Compare Source
Now also tracks non-plain objects (like
new User()).Thank you @barakyosi!!
PR: https://github.com/welldone-software/why-did-you-render/pull/179
CLOSED ISSUE: https://github.com/welldone-software/why-did-you-render/issues/74
v6.0.5Compare Source
fixed the bug "RangeError: Maximum call stack size exceeded" (#168) by making sure WDYR is not applied more than once under any circumstances.
v6.0.4Compare Source
v6.0.3Compare Source
v6.0.2Compare Source
v6.0.1Compare Source
Breaking Changes
Other Changes
v5.0.0Compare Source
Notice:
React@17is on it's way.Breaking changes:
useMemooruseCallbackresults:depschangesdepswere differentuseCallbackinvalidation due todepschanges (fixes #46)logOwnerReasonstrue by defaultbabel-plugin-lodashbecause lodash optimizations better are done by the user of the librarybabel-plugin-transform-classesbecause we build with a newer babel where it is not needed anymoreEnhancements:
For example for the following:
const sameObj = {a: {b: 'c'}}
ReactDom.render(<Main containerProps={{style: {height: '100%'}, className: 'default-highchart', sameObj}} />, domElement)
ReactDom.render(<Main containerProps={{style: {height: '100%'}, className: 'default-highchart', sameObj}} />, domElement)
Since props are equal by value, you will see the following option that allows for the generation of a detailed diff report:
Fixes
Readme
Dev
lint,test,audit, ande2e testsfor each PR.v4.3.2Compare Source
v4.3.1Compare Source
v4.3.0Compare Source
v4.2.7Compare Source
v4.2.6Compare Source
v4.2.5Compare Source
fixed WDYR trying to track untrackable React elements which resulted in a redundant console error to the console. thanks @MaffooBristol
v4.2.4Compare Source
fixed handling of hook state change during render. thanks @Hypnosphi!!
v4.2.3Compare Source
React.memo(null)raised a console error regarding WDYR failure.v4.2.2Compare Source
fixed a false positive regarding React elements with several children with different props:
https://github.com/welldone-software/why-did-you-render/issues/117
v4.2.1Compare Source
fixed false positive regarding different react elements (based on their props) reported as deep equlas
v4.2.0Compare Source
I came across situations where a component is re-rendered
because a property that holds a huge object deep equals to it's previous version is passed to it
(after a request to the API that returns the same result)
this caused my console to almost crash with tracks of every single nested property of it.
so now we would:
v4.1.3Compare Source
fixed a certain error when using with Preact.
Preact is not officially supported by the library but seems to work with it.
v4.1.2Compare Source
Improved readme to better explain how to add the library to projects without breaking hot reload
v4.1.1Compare Source
added logOwnerReasons by @Hypnosphi.
You can read about it here:
https://github.com/welldone-software/why-did-you-render#logownerreasons
added support to Sets tracking by @jfrumar-infinitusai
v4.0.8Compare Source
fixed a minor bug where no tracking was made if the previous value of a hook was falsy
v4.0.7Compare Source
Thank you very much @OliverJAsh for pr https://github.com/welldone-software/why-did-you-render/pull/104 <3
Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by WhiteSource Renovate. View repository job log here.