Describe the bug 🐞
In #4257 ObservableMixins.cs had a static constructor added, which enforces ReactiveUI to be fully initialized. This leads to innocuous helpers like ObservableMixins.WhereNotNull to suddenly break if used before RxAppBuilder.BuildApp is called.
As far as I can tell none of the helpers in ObservableMixins require initialization, but I am not sure if other Mixins (especially those in platform-specific modules) are affected.
Step to reproduce
- Use
ObservableMixins.WhereNotNull before ReactiveUI initialization
- Exception is thrown
Reproduction repository
No response
Expected behavior
Mixins that provide functionality not tied to ReactiveUI features should not require app initialization.
Screenshots 🖼️
No response
IDE
Visual Studio 2022
Operating system
No response
Version
No response
Device
No response
ReactiveUI Version
23.2.27
Additional information ℹ️
No response
Describe the bug 🐞
In #4257 ObservableMixins.cs had a static constructor added, which enforces ReactiveUI to be fully initialized. This leads to innocuous helpers like
ObservableMixins.WhereNotNullto suddenly break if used beforeRxAppBuilder.BuildAppis called.As far as I can tell none of the helpers in
ObservableMixinsrequire initialization, but I am not sure if other Mixins (especially those in platform-specific modules) are affected.Step to reproduce
ObservableMixins.WhereNotNullbefore ReactiveUI initializationReproduction repository
No response
Expected behavior
Mixins that provide functionality not tied to ReactiveUI features should not require app initialization.
Screenshots 🖼️
No response
IDE
Visual Studio 2022
Operating system
No response
Version
No response
Device
No response
ReactiveUI Version
23.2.27
Additional information ℹ️
No response