Avoid duplicate classes in MergedContextConfiguration #24532
I just noticed the following log while debugging some test context cache optimizations in one of my projects:
It's trimmed down, but as you can see
While not critical at all, I guess we can make an effort to avoid the duplicates. That should fix the logs and maybe saves a few cycles on the road (although that impact should be veeery small as the duplicates are filtered in
Let me know what you think.