Closed svenboulanger closed 1 year ago
As the BlazorMonaco.Environment
class is not currently used, I can remove it until it's used. But that will be just postponing the issue. Or, another similar name overlap may occur in any other place with any other namespace. I think the best way to handle this issue is using the full class name to get rid of the ambiguity, like you did.
When including
BlazorMonaco
andSystem
which would happen quite commonly, there is always an ambiguous reference toEnvironment
(like when usingEnvironment.Newline
).More of a user-experience issue than a bug though. People can simply qualify the full namespace where necessary.