-
-
Notifications
You must be signed in to change notification settings - Fork 84
refactor(RemoteChar): Reduce nesting #287
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
h2zero
left a comment
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.
Nice cleanup, thanks! Need to make some changes to retrieveDescriptors though.
|
Only part I'm unsure about right now is whether should be Also not sure if it's safe to group this check up with the others. Should it always return zero here or is it fine to return |
h2zero
left a comment
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.
Almost there 👍
h2zero
left a comment
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.
Couple of thoughts to extend the changes, let me know what you think.
|
Moved things around in |
101fbb9 to
ee374e7
Compare
h2zero
left a comment
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 to be a pain, just a couple minor items.
07d07e2 to
d64e087
Compare
h2zero
left a comment
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! Thanks!
|
@thekurtovic Could you please rebase this? Master added a check that should remain. |
b9a59e4 to
ca7502b
Compare
|
Still contains the change |
|
Might need to try again, I fixed the build issue but there is a merge conflict. |
167b73a to
ca7502b
Compare
|
If I resolve the conflict then it adds an additional commit to this PR. Am I supposed to squash everything into my main commit? |
|
I can squash the commits after when merging. |
* Renamed desc_filter_t to NimBLEDescriptorFilter * Added NimBLERemoteDescriptor pointer to NimBLEDescriptorFilter * retrieveDescriptors changed to take NimBLEDescriptorFilter pointer * General cleanup
|
Thanks, I rebased it and pushed back to your branch. |
|
Thanks, I was just about to try something myself. For future reference, would this have worked? Normally I just do |
|
All I did was: You could squash before or after this, usually easier before. |
|
Thanks. I was trying to rebase my branch after fixing the conflict but the rebase kept showing me commits from master only for whatever reason. I thought master was being merged into the branch opposed to the other way around. I need to lookup a git tutorial |
desc_filter_ttoNimBLEDescriptorFilterNimBLERemoteDescriptorpointer toNimBLEDescriptorFilterretrieveDescriptorschanged to takeNimBLEDescriptorFilterpointer