lonix1

You are right! Sorry, missed that. I always look into the corresponding parameter row in the table.

That PR was merged into version 38.0.0, and the current version on pypi is 41.0.1 - so it seems the upstream functionality is in place! (But I'm not a python...

Yes, exactly like in Visual Studio (i.e. not vscode). BTW [dupe](https://github.com/icsharpcode/ilspy-vscode/issues/28).

Yes that's true, there's a downside to both approaches. So agreed, a setting would solve the issue.

@jeffery9 If you got it to work, do you mind sharing the working config for docker, front and back?

Agreed, but that's the only way I could get it to start (even "localhost" and "0.0.0.0" didn't work). If it's on a firewalled local machine it's ok. Nonetheless, this docker...

This is from an older image that I created and it worked well for a long time: ```` SITES["api"]["domain"] = "localhost:8000" SITES["front"]["domain"] = "localhost:8000" ```` I decided to use this...

True. But keep in mind at least two people needed to hack that config option to get it to work. Maybe the problem is just us.

Actually, I'm unsure of this. Forgetting about the analyser for now (I just disabled it), I nonetheless get this exception; ````cs Exception thrown: 'Castle.DynamicProxy.InvalidProxyConstructorArgumentsException' in Castle.Core.dll ```` Weird, those args...

Your idea of a more descriptive warning is good. It will let the user know that it is "normal" and there is nothing he can do about it.