luvies
luvies
There isn't a recommended way, but it would be worth making one I think. I've seen something like the following used in Node DI frameworks: ```ts if (NODE_ENV === "production")...
This is a good idea, but if it's just a type-system trick, then this will work (without needing a wrapper class): ```ts export function sym(desc?: string): ServiceIdent { return Symbol(desc);...
I've seen other DI libraries with this and I do quite like it, it's just not been added before since I've not been sure on the best way to go...
I thought that might be a problem. Might be worth leaving the issue open anyway until that happens so people know that it is an issue currently. Also, good luck...
That example was pretty much what I was thinking, but whether it's worth implementing is mostly down to how well it fits. Using an API like Hapi's `ext` might be...
From what I've seen and read, all that's needed is to add the new target ```xml netcoreapp1.0;net452;netcoreapp2.0;netstandard2.0;netcoreapp2.1 ``` and then to add the following block to the csproj ```xml true...
I think I accidentally narrowed down the problem. If you remove the shebang, but leave the version directive on the second line, it does the same thing.
Alright, thank you! It might be worth removing it in that case, or at least specifying this in the documentation. I will just use the scripts without the framework directive,...
I will look into this when I can, in the meantime, is it still a problem? and if so, what would be the steps to reproduce (if you're not sure,...
The problem is with something in `AddBlockRestriction` not being initialised properly I think, but without more information I don't know if I can locate the issue. I will attempt to...