owenpahl commented on issue #6076: URL: https://github.com/apache/jmeter/issues/6076#issuecomment-1725225019
I've started digging into how this side of JMeter works. From what I can grasp the issue appears to be caused by two things: 1. The `HTTPSampler.image_parser` property is now retained when it is false (unselected), previously (v5.5) it was removed from the property map completely. This is possibly a side-effect of the move to the kotlin based schema model. 2. If a property is already defined, its value is not replaced by that in the config item property. Which I think in most cases would be correct (eg, if the domain is defined on a sampler this is take precedence over that in the config defaults), however for the boolean properties that map to checkboxes this means the default will never be applied as the property exists (with a value of false). Any thoughts on the correct way to address this? Do we change the behaviour back to removing false boolean properties? Or maybe define how values are replaced when there are defaults in scope better? I sure don't want to have to go back though all our existing scripts and enable downloading embedded resources on each sampler ... -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@jmeter.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
