Comments (5)
Good idea!
I had never thought of that use-case before, but it shouldn't be too hard to create a session-specific data store class. I'll add it to the to-do list.
In the meantime though, you can probably whip-up something that meets your needs pretty easily by inheriting from the DataStore
abstract class and implementing something similar to the MemoryStore
class, but with a bit of extra logic to separate the data by session.
from swagger-express-middleware.
well, browsing through the source, I spotted this:
// Get the current DataStore (this can be changed at any time by third-party code)
var db = util.isExpressApp(router) ? router.get('mock data store') || dataStore : dataStore;
I'm not sure this feature is documented anywhere, so I hope it's an intentional feature because it's allowed me to do this:
app.use(function(req, res, next) {
var cookie = req.cookies.__express_session_cookie;
if (cookie == undefined) {
console.log('CREATING NEW SESSION');
var randomNumber = Math.random().toString();
res.cookie('__express_session_cookie', randomNumber);
console.log('creating new data store for SESSIONID:' + randomNumber);
sessionDataStores[randomNumber] = prepareData();
app.set('mock data store', sessionDataStores[randomNumber]);
} else {
console.log('USING EXISTING SESSION');
if (!sessionDataStores[cookie]) {
// eg: you restart the server but use the same browser which kept
// the session cookie
sessionDataStores[cookie] = prepareData();
}
app.set('mock data store', sessionDataStores[cookie]);
}
next();
});
very very simple multi-session data storage. prepareData() is just returning a MemoryDataStore instance.
This is definitely better than messing around with key names.
from swagger-express-middleware.
here is something cleaner:
function createSessionStore(req, res, next) {
var cookie = req.cookies.__express_session_cookie;
if (cookie == undefined) {
var randomNumber = Math.random().toString();
res.cookie('__express_session_cookie', randomNumber);
sessionDataStores[randomNumber] = prepareDataStore();
app.set('mock data store', sessionDataStores[randomNumber]);
} else {
if (!sessionDataStores[randomNumber]) {
sessionDataStores[cookie] = prepareDataStore();
}
}
next();
}
Then you can use it like so:
app.use(cookieParser());
app.use(createSessionStore);
from swagger-express-middleware.
and my prepareDataStore() looks like:
function prepareDataStore() {
var myDB = new swagger.MemoryDataStore();
myDB.save(require('./dataEndpoint'));
return myDB;
}
and dataEndpoint.js would look like:
var swagger = require('swagger-express-middleware');
module.exports = new swagger.Resource('/endpoint', {
someKey: 'someValue'
});
from swagger-express-middleware.
Actually my little function had a bug.
function createSessionStore(req, res, next) {
var cookie = req.cookies.__express_session_cookie;
if (cookie == undefined) {
var randomNumber = Math.random().toString();
res.cookie('__express_session_cookie', randomNumber);
sessionDataStores[randomNumber] = prepareDataStore();
app.set('mock data store', sessionDataStores[randomNumber]);
} else {
if (!sessionDataStores[cookie]) {
sessionDataStores[cookie] = prepareDataStore();
}
app.set('mock data store', sessionDataStores[cookie]);
}
next();
}
This should be much better. I'll see if I can turn this into its own npm installable module (and of course, have some tests).
But I would need confirmation that the approach I'm taking is leveraging an intentional feature that will continue to exist.
from swagger-express-middleware.
Related Issues (20)
- Unit testing swagger-express-middleware with Jest and Supertest HOT 4
- NPM audit issue HOT 1
- Token scheme validation in case of defintion type: apiKey and Authorization header
- Old version of Multer is causing a high severity vulnerability HOT 1
- swagger-express-middleare not adding CORS headers HOT 1
- parseRequest - ability to skip multipart uploads HOT 1
- Way to cusomize http401 ? HOT 1
- FormData fields are undefined since switching to version 4.0.0 HOT 2
- validateRequest ignores "format": "uuid" for strings HOT 2
- Installing only devDependencies - `swagger-express-middleware` prevents `glob` from installing
- Does the file-based mock middleware support cross-file referencing? HOT 1
- what's the difference between @apidevtools/swagger-express-middleware and swagger-express-middleware? HOT 2
- npm lodash vulnerability CVE-2020-8203
- Support for Next.js
- Dicer Vulnerability HOT 2
- Dicer Vulnerability
- protobufjs Vulnerability
- ERR_HTTP_INVALID_STATUS_CODE
- Package is deprecated, migrating to express-openapi-validator
- This package is now closed
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from swagger-express-middleware.