exegesis-js / exegesis-express Goto Github PK
View Code? Open in Web Editor NEWExpress middleware to handle OpenAPI 3.x.
License: MIT License
Express middleware to handle OpenAPI 3.x.
License: MIT License
8.1.3
to 8.1.4
.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.
The new version differs by 4 commits.
0be88a0
fix: Use lodash version with prototype pollution fix (#578)
138fbc7
docs: Update Node version in the documentation (#579)
f9e5d7b
refactor: Use micromatch ignore
option instead of patterns with negations
6e32188
chore: Update yarn.lock
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
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.
1.2.3
to 1.2.4
.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.
The new version differs by 3 commits.
fd57754
ci: Upgrade dev dependencies. Don't fail on npm audit.
4c1e483
Merge pull request #29 from golopot/patch-1
ee0ba6f
fix: Fix type in readme
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
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.?
15.12.4
to 15.12.5
.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.
ci
option via API and config file (862ec4c)The new version differs by 8 commits.
649b530
docs: mention that debug
option is CLI only
862ec4c
fix: allow to set ci
option via API and config file
6b110b6
docs: switch to spectrum.chat
e4c6649
docs: syntax fixes in plugins list
6220641
docs: add @semantic-release/apm
to plugins list
a45273e
docs: add maven-semantic-release to list of community plugins
d109113
chore(package): update nyc and sinon
cd69583
test: delete unused test helper file
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
1.3.0
to 1.3.1
.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.
The new version differs by 26 commits.
252d303
Merge pull request #83 from exegesis-js/greenkeeper/semver-5.7.0
54eefd8
chore(package): update lockfile package-lock.json
1512617
fix(package): update semver to version 6.0.0
c7da3d9
Merge pull request #81 from exegesis-js/greenkeeper/mocha-6.0.0
8618068
chore(package): update lockfile package-lock.json
ba72515
chore(package): update mocha to version 6.0.0
1b333ee
chore: Upgrade tslint, other deps in lockfile.
f5f49dc
chore: Upgrade dev dependencies.
d913e4f
chore: Upgrade lodash and some dev dependencies.
9baf9aa
Merge pull request #78 from exegesis-js/greenkeeper/@types/node-10.12.24
9c3b72a
chore(package): update lockfile package-lock.json
5fcd523
chore(package): update @types/node to version 10.12.24
0ec661d
Merge pull request #77 from exegesis-js/greenkeeper/@types/node-10.12.23
d053b99
chore(package): update lockfile package-lock.json
c38c5f6
chore(package): update @types/node to version 10.12.23
There are 26 commits in total.
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
Exegesis become an indispensable part of development, thank you for your implement.
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.
// 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}`,
});
};
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}`,
});
};
// 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);
};
ExegesisResponse of ExegesisContext
to MyApiContext
at express middlewareI 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
2.2.2
to 2.2.3
.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.
The new version differs by 3 commits.
7069d42
Merge pull request #120 from exegesis-js/greenkeeper/semver-7.0.0
ac31bc0
chore(package): update lockfile package-lock.json
d29a7b5
fix(package): update semver to version 7.0.0
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
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.
5.2.5
to 5.2.6
.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.
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
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);
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.