Bryan Gonzalez

> We can see that this feature request generates lots of interest which means that there are legitimate and common use-cases that are / were not not well supported. I...

Mostly appveyor, sometimes travis On Fri, Jun 14, 2019, 2:22 PM Peter Bajurny wrote: > @bryan5989 what Ci system do you use? > > — > You are receiving this...

+1 winrm.Session.run_ps() returns all other streams besides output to stderr. winrm only seems to process error stream into human-readable, all other streams are still marked up, causes headaches for client...

@fehguy I disagree with your non-determinism comment. I argue that path resolution is non-deterministic by default. For example: ``` blog.domain/api/post/latest ``` Is deterministic because it always processes the same logic...

> @fehguy I disagree with your non-determinism comment. I argue that path resolution is non-deterministic by default. For example: > > ``` > blog.domain/api/post/latest > ``` > > Is deterministic...

Net core web api supports optional path (route) parameters. I have routes like: /api/chapter/{storyId}/{chapterId?} where if the chapterId is not specified, the first chapter is returned (or all chapters are...

see my rebuttal: https://github.com/OAI/OpenAPI-Specification/issues/622#issuecomment-701045346 @kurko there's not much to propose: make `required: false` legal in conjunction with `in: 'path'`

2 years later, I've realized that I misused the term resource in my final thought above (https://github.com/OAI/OpenAPI-Specification/issues/622#issuecomment-1067381861). That said, I restate my point that an OAS pathspec does not determine...

@nazidk We have an Win 7 Win 10 mixed environment and have no issues. We also have up to date .NET Frameworks on all systems (your admin workstation needs this),...

Try running PxtlCa.XmlCommentMarkDownGenerator directly from powershell, you should get some exception. In my case, I was using ghost doc, which has at least 2 xml elements that the generator doesnt...