Felix Leipold

`http://foo/bar + /path => http://foo/path` Is a severe regression against 2.6.1 which produced `http:/foo/bar/path`. Is there any intention maintain backwards compatibility?

This is an important issue for urban use cases. I am not sure whether the link above is still demonstrating the problem. I used this one (where the suggested route...

@fredbi surely you mean: ```yaml allOf: - $ref: ... x-go-custom-tag: xxx ``` It would be nice to be able to force the insertion of an `allOf` even for nested (not...

This really breaks the experience. Not being able to describe properties , which are declared as custom types (this issue also applies to `struct`s) makes it hard to produce usable...

Sounds like an interesting idea. How would you merge the two streams? Always one line at a time?

There are a couple of things, perhaps you would like to specify a prefix for each stream, so that you get something like this: ~~~ [stdout] I was printed on...

@ses1112 thank you for your contribution. These are interesting problems. As you have probably seen the documentation in README.md is generated from the acceptance test. It would be nice to...

@ansonliao Thanks for this interesting experience report. JProc is currently geared towards being called synchronously, that is one process after another. This means the last solution, while not very efficient...

Proper pipelining is currently a hassle to implement with JProc. In theory a pair of `PipeInputStream` and `PipeOutputStream` can be used to connect the output of one command with the...

@ansonliao good catch. The `withInput()` method was inadvertently set to be package private. I [fixed](https://github.com/fleipold/jproc/commit/3b13b658512024bd109fa04e1d7c4541dc112031) it to be public. The new release 2.3.0 has been pushed and is currently percolating...