Skip to content
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

plugins: allow plugins to provide a relative priority value #214

Merged
merged 1 commit into from
Oct 6, 2022

Conversation

wwade
Copy link
Owner

@wwade wwade commented Oct 6, 2022

The highest priority for a plugin is 0, the lowest is 1<<31. If there are multiple plugins providing a function at the same level, then it's down to the implementation in Plugins itself. Currently only getResources() combines the output from multiple plugins. workspaceIdentity() and workspaceProject() both return the response from the first plugin at a given level.

@wwade wwade enabled auto-merge October 6, 2022 01:48
@wwade wwade force-pushed the plugin-prio branch 2 times, most recently from 03857d8 to cb06a12 Compare October 6, 2022 01:51
The highest priority for a plugin is 0, the lowest is 1<<31. If there are multiple
plugins providing a function at the same level, then it's down to the implementation
in Plugins itself. Currently only getResources() combines the output from multiple
plugins. workspaceIdentity() and workspaceProject() both return the response from the
first plugin at a given level.
@wwade wwade merged commit 7b0a925 into main Oct 6, 2022
@wwade wwade deleted the plugin-prio branch October 6, 2022 02:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant