-
Notifications
You must be signed in to change notification settings - Fork 9
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
396 run middleware in application space #397
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the existing documentation there are more references to the middleware. Not all docs files have been updated and some, for example the Environments part, still references the old way for registering the middleware.
{ | ||
"middlewares": ["./myMiddleware"] | ||
} | ||
} | ||
``` | ||
|
||
It's only useful to add middleware to a node, gateway, proxy and standalone service because they are actively involved with the communication system. Adding middleware to a repository service won't result in an error, but doesn't have any effect either. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With the new implementation we cannot add middleware to the repository anymore. This paragraph should be removed or rewritten.
Fixes #396
Changes proposed in this pull request:
@MaskingTechnology/jitar