Aleksey Usatov
Aleksey Usatov
I have a similar problem. I have a type with required fields. I'd want to rely on json serializer to throw serialization exception if it can't correctly deserialize required fields,...
Could you at least add something like `fnm env --json` with outputting only fnm related variables there (without modified `PATH` that is)? In that case we could maintain fnm integration...
This could also solve fnm integration story with other non-supported shells like nushell as well.
I'd really like to have this feature. I'm trying to write a DSL for Gitlab CI and because of this behaviour I have to resort to a bunch of nasty...
This issue is a part of #14 and will be solved together with it.
Upon thinking about this there should be actual middlewares like in ASP.NET Core to properly manage this shared context. So they can cleanup after themeselves after each subsequent middleware invocation....
So, the problem is due to Telegram disabling everything older than TLS v1.2 (which is not used as the default in .NET Framework 4.5). The best way to mitigate this...
Yes, that's the expected behaviour, it's the same as with previous events in the client. If there's an exception in user code we can't do anything other than stop execution.
> I'm curious as to why the library wasn't designed this way, because it makes much, much more sense like this. This applies to things like Message.Type, etc. as well....
I think it should be a property on request base class to allow per request setting. And it means that we need to implement all Bot API methods in terms...