Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Transports, streams and buffers #8

Merged
merged 1 commit into from
Nov 25, 2018
Merged

Transports, streams and buffers #8

merged 1 commit into from
Nov 25, 2018

Conversation

feugy
Copy link
Owner

@feugy feugy commented Nov 25, 2018

Added

  • Support for Buffer and Stream parameters and results
  • Transports for a better extensibility, and the corresponding getClient()'s transport.type option (default to local transport)
  • init() method is now optional: initialization will occur at first call if needed, whatever transport used
  • Usage of Yarn

Fixed

  • client.exposed contains the exposed descriptor, even with local transport (only http transport used to have one)
  • Http errors are now wrapped in Boom errors with http transport (only local transport was propagating them)

Changed

  • getClient() always throws synchronous validation errors.

  • When called, init() always refresh the exposed APIs.
    This allows to force initialization proactively when suspecting a remote service change.

    Previously it was feching exposed APIs only once.

  • Use got instead of request-promise-native.

    Thrown Error codes and message may be slighlty different.

  • Reformat CHANGELOG to follow Keep a Changelog recommandations

  • New documentation with latest docma v2.0.0

  • Dependencies update

Added
- Support for Buffer and Stream parameters and results
- init() method is now optional: initialization will occur at first call if needed, whatever transport used
- Usage of Yarn

Fixed
- client.exposed contains the exposed descriptor, even with local transport (only http transport used to have one)
- Http errors are now wrapped in Boom errors with http transport (only local transport was propagating them)

Changed
- Reformat internals to introduce transports: better extensibility
- Breaking: buildClient() throws only asynchronous validation errors  (name and version when using local service).
  Previously those errors were thrown synchronously.
- Breaking: when called, init() always refresh the exposed APIs.
  This allows to force initialization proactively when suspecting a remote service change.
  Previously it was feching exposed APIs only once.
- Breaking: use got instead of request-promise-native.
  Thrown Error codes and message may be slighlty different.
- Reformat CHANGELOG to follow Keep a Changelog recommandations
- New documentation with latest docma v2.0.0
- Dependencies update
@coveralls
Copy link

coveralls commented Nov 25, 2018

Coverage Status

Coverage remained the same at 100.0% when pulling a5b09ef on transports into 96594d6 on master.

@feugy feugy merged commit 6e9d734 into master Nov 25, 2018
@feugy feugy deleted the transports branch November 25, 2018 15:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants