Igor Savin

Considering all the problems with Travis (https://news.ycombinator.com/item?id=25338983, https://arstechnica.com/information-technology/2021/09/travis-ci-flaw-exposed-secrets-for-thousands-of-open-source-projects/), would you be open to a PR that would migrate CI to GitHub Actions instead?

TS types for oas-validator

1

### Detailed Description oas-validator is missing TS types, which makes consuming it from TS projects rather inconvenient. We (Lokalise) can contribute the types, in case they would be accepted by...

Support .examples()

7

JSON Schema supports `examples` keyword (see https://json-schema.org/draft-06/json-schema-release-notes.html) which is helpful for providing examples of a given schema. While not used for validation, it is very valuable for JSON Schema and...

Missing documentation for registering new consumers

1

Neither from readme, nor from examples it is clear how one would register a new consumer for particular queue.

Fixes https://forums.meteor.com/t/solved-error-handler-with-name-u-already-exists/23910

Support for Oracle

1

At this point "Could not get the sql to select table names from client: oracle" is returned when cleaning for Oracle database is attempted.

Sometimes it is beneficial to be able to turn off the validation part of `safeParse` while preserving the serialization part of it. Most common example - enabling reply validation in...

Enable Travis builds for the repo

1

Would really simplify pull request quality check if tests would be automatically running against them.

Add diagnostics_channel hooks

1

See https://nodejs.org/api/diagnostics_channel.html Consider using https://github.com/simon-id/diagnostics_channel-polyfill#readme polyfill for older Node versions.