Roman Sainchuk

For `description` and `summary` - take it from first document For `servers` - create unique array by `url` from both documents @adamaltman @RomanHotsiy please advice how to join `parameters` ?...

> Can you exclude prettier changes from this PR? It's hard to review :( removed

LGTM 👍

Hello @akx In `1.0.0-beta.108` was added browser support. We're still depending on `colorette` but it is not used in browser env (replacement for `node-fetch` is still in progress but you...

In case we have assertion like this (I know it doesn't make much sense but Im interested in implementation behaviour): ```yaml assert/put-200-and-201: subject: - ResponsesMap if: - subject: - PathsMap...

I'd say to support array only for top level `subject` field. As for me its not clear how it supposed to work if we have several items in `where` list...

> Add support for 3 additional locator properties: `filterInParentKeys`, `filterOutParentKeys`, `matchParentKeys` (regex). See the docs for more details. From my understanding these properties are mutually exclusive along with `property` locator....

We had a small discussion with @ohorbachevskyi about new syntax and ended up with idea to put top level `subject`, `property`, new locators and assertion inside `do` block. So this...

Hello @ArtiomTr First of all I was wrong about > Currently this action doesn't fail (or report error) if any of the thresholds aren't met I've updated action to latest...

Also, what do you think about creation the same table with coverage for each `coverageThreshold` entry ? Everything remains the same but in case we have jest config like I...