WIP: Exclude init initializer from plugins list command count #771
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@jaredcwhite I put the tests in a separate commit and this PR in WIP because I found myself unable to set up a valid site configuration to test the CLI commands :/ What could I have missed? Could you point me in the right direction? |
akarzim
force-pushed
the
fix/plugins-list-count
branch
from
1769687
to
a8915a7
Compare
|
I'll try to get this over the hump for v2.0. Apologies for the long delay! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a 馃悰 bug fix.
Summary
This PR excludes
init (Initializer)from the count of registered plugins when thebin/bridgetown plugins listcommand is run. See #770 for details.Context
Fixes #770