Skip to content
This repository was archived by the owner on Apr 14, 2022. It is now read-only.

Add koa@next support#97

Closed
cristiancavalli wants to merge 1 commit intoGoogleCloudPlatform:masterfrom
cristiancavalli:add-koa-next-interface
Closed

Add koa@next support#97
cristiancavalli wants to merge 1 commit intoGoogleCloudPlatform:masterfrom
cristiancavalli:add-koa-next-interface

Conversation

@cristiancavalli
Copy link
Copy Markdown
Contributor

@cristiancavalli cristiancavalli commented Jan 20, 2017

  • Add interface for koa@next through .koaNext
    method property.
  • Add documentation to readme and new code.
  • Add tests and server scaffolds.
  • Add npm-install-version as development
    dependency to use koa@next scaffolds.

@cristiancavalli cristiancavalli force-pushed the add-koa-next-interface branch 2 times, most recently from 1a6ed1c to 77cb5ba Compare January 20, 2017 17:55
  - Add interface for koa@next through .koaNext
    method property.
  - Add documentation to readme and new code.
  - Add tests and server scaffolds.
  - Add `npm-install-version` as development
    dependency to use koa@next scaffolds.
@cristiancavalli
Copy link
Copy Markdown
Contributor Author

@GoogleCloudPlatform/node-team ptal

Comment thread README.md

// Will attach to 'error' event which includes
// request/response lifecycle errors
errors.koaNext(app);
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Quick question: I would assume that koa@next moves pretty fast. Do we think this integration would be stable, i.e. we won't be broken as koa@next changes?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ping

Copy link
Copy Markdown
Contributor Author

@cristiancavalli cristiancavalli Jan 30, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it would be stable for our purposes and the API surface which we wish to exercise. It may break though given that it's OSS and in-development. These mocks are meant to break, though, given that the API surface changes so that we can know about it

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ofrobots ping

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ack.

@@ -0,0 +1,46 @@
/**
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Like with the express5, how is this file hooked into the tests?

@cristiancavalli
Copy link
Copy Markdown
Contributor Author

@ofrobots None of the scaffold servers are hooked into automated test runs like we discussed before

@DominicKramer
Copy link
Copy Markdown
Contributor

Any further work in this area will be done in the google-cloud-node/error-reporting repository and is being tracked by issue 2295 in that repository.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants