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
Restructure project + server plugins #837
Conversation
6604169
to
5f165fd
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@TheArcaneBrony pointed out there is no way to restrict a plugin's capability with this PR
one should be able to restrict which components and users the plugin can act on
This could be resolved by having an "official" plugin repository, with plugins that are checked and verified to be following policies and not doing dodgy things. For externally sourced plugins, it would be up to the user to read and understand the code. |
99d453a
to
5473e07
Compare
fafd950
to
b1bd129
Compare
a44087b
to
192dbca
Compare
401eda0
to
baeec00
Compare
a7b2946
to
285fb6a
Compare
285fb6a
to
606a710
Compare
http error data field, migrations
fixup! Cleanup, reformat, fix some todos, git hook
606a710
to
5c146b1
Compare
Gonna close this for now, because the only relevant part now is the plugin system. Should make a new PR with just the plugin system code at some point, if we still want server plugins? |
Assignments
samuel: code
matteo, arcane, erkinalp: review
cat: documentation