Tim Roberts

I've also tried building `davidfowl/dotnet-5` and get errors related to a missing `Connections` namespace: ``` Abstractions/ConnectionBuilderExtensions.cs(6,18): error CS0234: The type or namespace name 'Connections' does not exist in the namespace...

I really like this. As you mention, this _ambient_ context pattern can be useful for lots of use-cases and having tighter language support for it sounds like a great idea...

While you may have many 'things' in scope, a function would only have to declare an explicit parameter for the things that it requires access to. If a function is...

> Sure, but my suspicion is that typical functions will want to access (or at least reserve the right to access) several ambient resources [...] So this proliferation of having...

The original experiment was to build something that was more aligned with SpecFlow (since we were .NET Developers). TypeScript decorators was the key enabler of that. SpecFlow has notions of...

Thanks for coming onboard @Fryuni! With regards to releases, I was: - doing active development on `master`. The `release` action can be run against any branch, but from `master` the...

The `release` workflow simply calls `npm publish`. So you're correct, no dist-tag information is included. It shouldn't take too much work to modify the workflow to call npm again to...

As the above mentioned ticket eludes, tsflow is adapting CucumberJS to make it more object-oriented. The idea is that the class itself becomes your world (since `this` would represent a...

I noticed in the `package.json` in your screenshot, that you're referencing `cucumber`. Could you change this to `@cucumber/cucumber` and try again. They are scoping the package from version 7, and...

Yes, this project grew out of an experiment with TypeScript decorators to see if I could build something that presented an API surface that was more akin to SpecFlow in...