Discussed in #3313
Originally posted by KevinBrogan February 23, 2022
I can setup a reaction and pass it the options {requiresObservable:true} to turn on the config warning for just that one reaction, instead of turning them all on with configure({reactionRequiresObservable: true}), but I can't do the opposite.
I would like to be able turn off the global config on a case by case basis.
My use case is dealing with user generated code, and the user may decide to not output an observable property value. I can't leave warnings on for my code and off for user code but that would be very useful.