Kasper Kondzielski
Kasper Kondzielski
So I was thinking about possible dsl for server variables and we cannot use endpoint dsl here because of two reasons: - variables can be anywhere e.g. schema could be...
I think that when we extend tapir model to fully support all the open api cases there will be no need to create open api objects in a different way...
I agree that you might not want to use tapir to create an http4s implementation for you. But despite the complexity of such hand crafted implementation it will still be...
I think that you are not calling `protocol.cancel` when the session resource is being released, although I tried such quick fix myself and it didn't help so there must be...
thanks for the honest answer. I appreciate it 👍
> nvim-next: map builtin_T_expr with {expr=true} instead. This is supposed to appear only if you bind accidentally builtin functions without passing `opts.expr=true`. Builtin functions do set this in their definition...
Sorry, I was quite busy. I am going to take a look at it. > I love the concept and it is something we should do. I am glad to...
In the end I was able to simply replace the iterator with accessing node's siblings via `node.parent.nodes`. With this the user side function for my particular use case looks as...
>  > > That parameter is not used and thus can be removed. Right, I always forget that this is possible in dynamically-typed languages :+1:
> > Any idea how to fix it? > >  > > status is not a parameter for `function Explorer:expand(node)`, looks like it's unused. It must have changed once...