Why are the Uno Authentication Providers (e.g. Web) using OptionsSnapshot instead of OptionsMonitor? (Because WritableOptions only supporting Snapshot, not Monitor...)

[DevTKSS]

Checking out currently the src code of exisiting definitions and read for another project about IOptions for CI/CD integrations, so I am wondering why those are not using IOptionsMonitor 🤔 maybe somone can explain this 👍

uno.extensions/src/Uno.Extensions.Authentication.UI/Web/WebAuthenticationProvider.cs

Line 8 in 48d100b

IOptionsSnapshot<WebConfiguration> Configuration,

Edit:
I think I found the reason, while the answer is not really satisfying:

https://github.com/unoplatform/uno.extensions/blob/main/src/Uno.Extensions.Configuration/IWritableOptions.cs

the Uno.Extensions.Configuration which we use for example to get WritableOptions are only using IOptionsSnapshot<T> but not IOptionsMonitor<T> which is e.g. for Api requests using CI/CD integration

reference I discovered IOptionsMonitor<T> which explains also a good reason why we should maybe want to have it available in the future:
https://www.youtube.com/watch?v=wxYt0motww0

or even listening for Options Changes possibly also through Hot Reload, which is stated to be limited to not update-able because of the Windows Provided Hot Reload.
So possibly this could even be used to workaround this in our uno apps 🚀 but only if we would be able to have not only a OptionsSnapshot<T> 🫤

• [HotReload] appsettings.<ownKey>.json changes and Resource defined Items are not applyed on HotReload uno#20452

[DevTKSS]

@jeromelaban Not sure if the team could evaluate this for improvements in the future, so just wanted to let you know about this.