We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Plugins have priorities. This is good.
What is not good is that the priorities are hard-coded integers in the body of each plugin.
That should go away.
Instead, plugins should get priorities based on the order they're declared in the settings file.
The top plugin in the list should have the highest priority, and the bottom plugin should have the lowest.
This makes priorities sort of ephemeral per time the config is read but that is ok because they can and should change as needed.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Plugins have priorities. This is good.
What is not good is that the priorities are hard-coded integers in the body of each plugin.
That should go away.
Instead, plugins should get priorities based on the order they're declared in the settings file.
The top plugin in the list should have the highest priority, and the bottom plugin should have the lowest.
This makes priorities sort of ephemeral per time the config is read but that is ok because they can and should change as needed.
The text was updated successfully, but these errors were encountered: