You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks so much for this great module, it's saved me a lot of time already 👍. Something helpful would be if there was an option for Find the Culprit to automatically enable the dependencies of the modules when testing through iterations, and when picking the initial modules that should stay enabled. Without those dependencies, the tested modules may not be fully enabled and therefore we wouldn't get the real results.
I also noticed that when choosing the modules to keep enabled, the order is not quite alphabetical (it's like it's going through several lists, each of them in alphabetical order, but not a global alphabetical list. This makes finding the right module difficult when it's in a long list).
The text was updated successfully, but these errors were encountered:
Enabling the dependencies when running is really necessary, I keep running into issues when trying to find a conflict as some modules will not load (or worse cause more issues) if run without their dependencies.
Thanks so much for this great module, it's saved me a lot of time already 👍. Something helpful would be if there was an option for Find the Culprit to automatically enable the dependencies of the modules when testing through iterations, and when picking the initial modules that should stay enabled. Without those dependencies, the tested modules may not be fully enabled and therefore we wouldn't get the real results.
I also noticed that when choosing the modules to keep enabled, the order is not quite alphabetical (it's like it's going through several lists, each of them in alphabetical order, but not a global alphabetical list. This makes finding the right module difficult when it's in a long list).
The text was updated successfully, but these errors were encountered: