-
Notifications
You must be signed in to change notification settings - Fork 225
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
On connect dialog, in the directory list, remove 'Custom' and add all custom central servers #1894
On connect dialog, in the directory list, remove 'Custom' and add all custom central servers #1894
Conversation
Hi @jp8 thank you for your contribution. The style doesn't seem to be right. Could you please have a look at clang format? Also would it be possible to have screenshots? |
Ok. Wasn't up to date with the other PR. Once the artifacts are built - and I find time - I'd be happy to test your proposal. From a first glance it looks interesting ;-) |
BTW, you can run |
Thanks - I did try that approach several weeks ago but got errors, likely due to an old clang-format in Debian 10. |
I tried to write it in a way that would remain compatible with all the other proposals that are still under discussion in #1884 |
Yeah. Not a big deal since the check now seems to be ok. After having compiled it I'd say I'm quite happy with this change! What about:
|
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.
Quite small but effective ;-)
I do think an edit button or link that opens the settings dialog to the correct page is the likely best way to get to the management interface. But there might be a lot of discussion and ideas around that, and I don't think this small pull request depends on it. Could we save it as a separate topic ? |
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.
Sorry I can't really comment, this week on vacation with only a cellphone.
By the way, feel free to
to refresh your local git and then
and squash history (use "fix" if you want). I don't think any of us review on a commit by commit basis and the extra commit history will need cleaning up before it's merged. |
- remove Custom from list - add the user's custom central servers to the list Fix code formatting More fixes to coding style Fixed code comment Improved code comments to clarify how iCustomDirectoryIndex is used. Further code comments
rename cbxCentServAddrType to cbxDirectoryServer Fix code formatting renamed handler OnCentServAddrTypeChanged -> OnDirectoryServerChanged
…m central servers
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.
Please use pljones suggestion to rebase your work: #1894 (comment)
Doing it with a merge makes stuff complicated
Sorry to be a pain but in the interests of clarity, can you detail why you agree, against the points made here? #1884 (comment) |
I am really sorry to be so new to git. I did follow the steps from pljones but on my next attempt to push, it left me with: hint: Updates were rejected because the tip of your current branch is behind ...and asked me to pull from my feature branch to local and then merge conflicts. I am guessing that after following the steps, I should have pulled from my feature branch, before doing any further work. |
No. That’s what I‘d suggest to undo the merge, and then force push everything. |
OK I will figure out how to do that. If I understand right, the goal is to take the 20 commits that are now on the feature branch in my fork, and condense them into just one or a few commits... is it right ? |
Kind of. Yes: Multiple (or one) commit/s based on the latest master code. You‘d git checkout this commit: 79559e5 git push HEAD to your feature branch (https://stackoverflow.com/a/40929378) and then use git rebase -i to bring the commits together. |
09746ee
to
79559e5
Compare
I think I've done all this. I condensed it to 7 commits. Is it ok ? |
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.
From a first glance this looks much better now ;-)
Is there anything more I need to do, in order to get this merged ? |
There are still some unresolved review comments above. |
centservaddrtype is set to AT_CUSTOM.
ok all done i think. |
Last steps:
Anything else? Could you please copy and paste this check list in your first post above? |
I was already on this list, from contributions I gave directly to Volker in the past. |
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.
I'm happy with it now. (Subject to the TODO item getting done ASAP.)
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.
Looks OK to me. I‘ve tested an early version and the code looks ok.
This should be squash&merged. |
I couldn't get the github UI to do what I wanted, so I did it locally, hence I'm going to close this. |
There’s an arrow next to the merge button with which you can change it to squash and merge? |
I don't think that lets you adjust the commit message and it's as if the branch never existed and a single commit to master happened directly. At least I think that's what happened when I first tried it. I wanted to show a merge from a branch with a single commit from jp8 with a sane commit message. |
So at the end I should have sqashed again, into a single commit ? (just so I know for next time...) |
Yeah, it can sometimes help to keep the history (it recently let me split a change into to two PRs) but generally, once final, one commit is preferred. |
On the connect dialog, in the directory (custom central server) list,
Addresses discussion #1869
Is an alternative to pull request #1884
It is a change to the UI. If the pull request is accepted, I will make a corresponding pull request to the website documentation.
Working implementation
It's a UI change so testing and feedback are appreciated. It is one alternative UI among several that are under discussion in #1869 and #1884
Checklist
Last steps: