Middleware structure and name changes
Closed this issue · 1 comments
As referenced in #70 and originally discussed in #64, we need to break apart "collective" packages to give users individual choice, but also have an overall "suite" install still in place. While looking into this for my recent Watson integration, I realized that we ended middleware packages with "middleware", and likely put that in the wrong place.
As per my PR, we probably want to do something like this:
- botbuilder-middleware
- botbuilder-middleware-engines
- botbuilder-middleware-text-analytics
- botbuilder-middleware-watson-nlu
...which would mean changing something like "botbuilder-text-analytics-middleware" to "botbuilder-middleware-text-analytics". This is better in my opinion because of tab completion and search.
If implemented, however, it would require changes to the folder structure and NPM package (deprecating old ones) for the above, as well as the spell check and recognizers middleware to bring everything into alignment.