Immutable Service Options
I have a service which mutates its options. I discovered that IOptions<T> creates a singleton and all of the unit tests I'm running all get the same options but unrelated services are mutating the options and other services are seeing those changes.
I'd like to have a simple solution that would ensure the options are not mutated and should something try to, it breaks or doesn't compile or whatever.
If there's a simple solution, what is it?
Someone in the chat yesterday mentioned something about IImmutable, but I don't know the specifics.
I saw something about an ImmutableDictionary, but I'd like the whole class to be.
Ideas?
I kind of think this should be a standard of some sort.
5 Replies
When the tests are ran individually, they all pass. When ran concurrently, they fail because of this mutation.
are tou storing state in IOptions?
that's not what they're for
with that said, you can inject an option snapshot
So remove the code that is doing the mutation. You're not supposed to do that.
Unknown User•3mo ago
Message Not Public
Sign In & Join Server To View
Yeah, I'm migrating a ton of .NET framework projects and they already have tests that are using the old static configuration methods which create new objects. I know now not to mutate options, but it'd be nice to have a fool-proof way to enforce immutability