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
Add-ons #5950
Add-ons #5950
Conversation
Codecov Report
@@ Coverage Diff @@
## master #5950 +/- ##
==========================================
+ Coverage 89.19% 89.23% +0.04%
==========================================
Files 162 163 +1
Lines 11287 11369 +82
Branches 1833 1844 +11
==========================================
+ Hits 10067 10145 +78
- Misses 928 930 +2
- Partials 292 294 +2
|
There is a big inconsistency problem nere: "addon" vs "add-on". |
Yes, it would be great if we could normalize it as ”add-on” outside code. No strong opinion on the code side (AddOn vs Addon). |
Thanks! |
🤯 |
This is #1272, updated to the current code and with builtin-addons removed. There should be some unanswered questions in that PR. I've addressed some of the simplest feedback and made the CI pass, though there are still documentation references to file paths and there may be other things that need to be fixed.
I haven't thought much about the implementation itself yet, but I already have a question "how can a user override a priority of a middleware set by an addon or replace that middleware with their own subclass of it".
Closes: #1272, fixes #5992