QuarkusTestExtension#runExtensionMethod() should only deep clone when necessary
See original GitHub issueDescription
QuarkusTestExtension#runExtensionMethod()
appears to do a deep-clone of all arguments of a given test method. If the parameter class is the same in both class loaders (i.e. both loaded it through a common ancestor class loader) this wouldn’t be necessary and avoiding the deep-clone would also be desirable because not all objects can be cloned (see #9677).
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Should you deep clone nested properties?
You don't need to deep clone when mutating state. If you only need to change one of the basic props of your object,...
Read more >Methods for deep cloning objects in JavaScript - LogRocket Blog
There are several ways to shallow clone objects in JavaScript, but deep cloning objects is trickier. We highlight several methods to do so....
Read more >Deep-copying in JavaScript using structuredClone - web.dev
The platform already needed the ability to create deep copies of JavaScript values in a couple of places: Storing a JS value in...
Read more >How Deep Cloning Objects in JavaScript Works - DigitalOcean
Reassigning objects to new variables only creates a shallow copy of the original object. In the next step, you will explore how looping...
Read more >In Redux, is it necessary to do deep copy - Stack Overflow
Can I do it as above? that I just assign the whole object to data without copying? or const rootReducer = (state =...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@stuartwdouglas has already chatted with the JUnit team about this, so they are aware of our case
Hopefully we won’t have to create a more clever cloning algorithm, but it may come to that at some point…