exegesis-js / exegesis-express Goto Github PK

The devDependency lint-staged was updated from 8.1.3 to 8.1.4.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

lint-staged is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

There's a dummy typo occurred in README file in the server section. That might happened due to the old version described in readme.
So, basically, to fix this typo replace this example code snippet:

 const exegesisMiddleware = await exegesisExpress.middleware(
        path.resolve(__dirname, './openapi.yaml'),
        {ignorePaths: true}
    );
    app.use('/api/v2', exegesisMiddleware);

With this:

const exegesisMiddleware = await exegesisExpress.middleware(
       path.resolve(__dirname, './openapi.yaml'),
       {ignoreServers: true}
   );
   app.use('/api/v2', exegesisMiddleware);

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

The devDependency supertest-fetch was updated from 1.2.3 to 1.2.4.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

supertest-fetch is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Hi Team,
[email protected] is a indirect dependency for exegesis-express and this version has vulnerabilities. Dependency is exegesis-express -> [email protected] -> [email protected]. Can you please change the exegesis dependency version from 3.0.1 to 4.1.0.?

https://snyk.io/test/npm/exegesis-express/3.0.0

The devDependency semantic-release was updated from 15.12.4 to 15.12.5.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The dependency exegesis was updated from 1.3.0 to 1.3.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

exegesis is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

First

Exegesis become an indispensable part of development, thank you for your implement.

Ask

How to access ExegesisContext at express midleware (app.use)
I want to access ExegesisContext for response at presenters/.ts , not controller/*.ts in Clean Architecture
For realize above, I think the way that setting ExegesisResponse of ExegesisContext to MyApiContext as property in middleware(app.use).

But i don't success it.

Example that i want

// controller/hello.ts
const hello = async (ctx: ExegesisContext) => {
  const name = ctx.params.query.name;
  usecases.sayHello(name);
};

// usecase/hello.ts
const sayHello = async (name: string) => {
  presenter.renderHello(name);
};

// presenter/hello.ts
import { myApiContext } from '../../';

const sayHello = async (name: string) => {
  myApiContext.exegesisRes.status(200).json({   // ✅ this is the way i want
    message: `Hello ${name}`,
  });
};

The way realize the above 3 pattern.

Parttern1 - Across layer with exegesisContext as arguments

// controller/hello.ts
const ping = async (ctx: ExegesisContext) => {
  usecases.sayHello(ctx);
};

// usecase/hello.ts
const sayHello = async (ctx: ExegesisContext) => { // ✅
  presenter.renderHello(ctx);
};

// presenter/hello.ts
const sayHello = async (ctx: ExegesisContext) => { // ✅
  ctx.res.status(200).json({ 
    message: `Hello ${ctx.params.query.name}`,
  });
};

Parttern2 - Set ExegesisContext to MyApiContext at controller and 1st line of each action.

// controller/hello.ts
const ping = async (ctx: ExegesisContext) => {
  setExegesisContext(ctx) // ✅ if i do, i realize response at presenter layer,  but i have to write same code every time at action.
  usecases.sayHello(ctx.params.query.name);
};

Parttern3 - Set ExegesisResponse of ExegesisContext to MyApiContext at express middleware

I don't success it.
Can we access ExegesisContext that has response writer at express middleware(app.use) ?
If it success, it will be better code than pattern1 and pattern2.

Thanks.

Please raise issues here:
Currently I am getting this issue when running tsc :

node_modules/exegesis/lib/types/bodyParser.d.ts:2:8 - error TS1192: Module '"http"' has no default export.

2 import http from 'http';
         ~~~~


Found 1 error.

I can see you guys fixed this issue but the change hasn't been pushed to yarn/npm users and the package is still at 1.0.0
https://github.com/exegesis-js/exegesis/issues

The dependency exegesis was updated from 2.2.2 to 2.2.3.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

exegesis is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Due to issues with exegesis 3.0.0 outlined in exegesis-js/exegesis#262 , could the exegesis package be upgraded to 3.01 and release a new version of exegesis-express be released.

Thanks.

The devDependency @types/mocha was updated from 5.2.5 to 5.2.6.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/mocha is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

    const exegesisMiddleware = await exegesisExpress.middleware(
        path.resolve(__dirname, './openapi.yaml'),
        {ignorePaths: true}
    );
    app.use('/api/v2', exegesisMiddleware);

Should be...

    const exegesisMiddleware = await exegesisExpress.middleware(
        path.resolve(__dirname, './openapi.yaml'),
        {ignoreServers: true}
    );
    app.use('/api/v2', exegesisMiddleware);