-
Notifications
You must be signed in to change notification settings - Fork 71
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
Custom Middleware Reusability #334
Comments
Hey @cschuff, Could you please add some details on your use case? We discussed generating unique IDs for custom middlewares during their implementation. However, we were concerned how one could reference the middleware in the "customMiddleware" configuration without knowing the generated ID. Why do you need the same middleware to be added multiple times? Is it to use different mount paths? Or a different order? Thanks! |
I have a generic |
… of the same custom middleware Similar to the implementation for custom tasks: https://github.com/SAP/ui5-builder/blob/d60c67dafc6d96a8345da2004972cd4b839eece6/lib/types/AbstractBuilder.js#L81-L89 Resolves #222
… of the same custom middleware Similar to the implementation for custom tasks: https://github.com/SAP/ui5-builder/blob/d60c67dafc6d96a8345da2004972cd4b839eece6/lib/types/AbstractBuilder.js#L81-L89 Resolves #222
tried it out - see SAP/ui5-server#246 (comment) |
remove custom @ui5/server reference PoC for https://github.com/SAP/ui5-server/issues/222
… of the same custom middleware (#246) Similar to the implementation for custom tasks: https://github.com/SAP/ui5-builder/blob/d60c67dafc6d96a8345da2004972cd4b839eece6/lib/types/AbstractBuilder.js#L81-L89 Resolves #222
Expected Behavior
Defining a custom middleware once should allow to reuse it in
customMiddleware
more than once. This might be achieved by giving middlewares an id (to reference custom middlewares) and a name (used for order and display).Current Behavior
It fails with
duplicate middleware name
:Steps to reproduce the issue
Affected components (if known)
Log Output / Stack Trace
The text was updated successfully, but these errors were encountered: