-
-
Notifications
You must be signed in to change notification settings - Fork 632
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
Expose player info forwarding in the API ( Fix #1063 ) #1064
base: dev/3.0.0
Are you sure you want to change the base?
Conversation
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.
Thanks! 😀 (The CI fails due to an incorrect order of imports)
Hang on, gotta make checkstyle happy with the import order |
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.
This requires approval by @astei as he made a very deliberate effort in ensuring this does not get exposed to the API.
May I ask the reason? |
The intention is to avoid exposing implementation details to plugins, especially given that things like Configuration are not API I do wonder the use-case for this sorta thing, the forwarding mode should be effectively transparent to plugins, and have no real impacts elsewhere |
My practical use case is setting up nano limbo on-demand from the proxy. To do so, I need to forward the forwarding configuration to it. |
Any update? |
Fix #1063