-
Notifications
You must be signed in to change notification settings - Fork 216
Doc for backward blind #685
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
Conversation
Signed-off-by: Alberto Tudela <[email protected]>
Signed-off-by: Alberto Tudela <[email protected]>
Signed-off-by: Alberto Tudela <[email protected]>
Co-authored-by: Steve Macenski <[email protected]> Signed-off-by: Alberto Tudela <[email protected]>
Signed-off-by: Alberto Tudela <[email protected]>
Signed-off-by: Alberto Tudela <[email protected]>
Signed-off-by: Alberto Tudela <[email protected]>
Co-authored-by: Steve Macenski <[email protected]> Signed-off-by: Alberto Tudela <[email protected]>
Can you resolve :-) |
Signed-off-by: Alberto Tudela <[email protected]>
Signed-off-by: Alberto Tudela <[email protected]>
|
Done! |
Thanks 😆 I'll merge this now but the main PR I'll wait on CI before merging just to sanity check -- but you can consider this done! did you want to backport this to the Humble version in the other repo? |
Sure! |
In humble, the direction/backward parameter is still on the server side. How do you want to handle this? |
Add the blind bit on the server side too I guess. Maybe we should have in the main version the same backporting warnings if the blind docking is set in the server rather than plugin for future migrations. We can just throw and require an update for this feature rather than trying to handle it for them automatically |
No description provided.