-
-
Notifications
You must be signed in to change notification settings - Fork 510
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
Consolidate components #2169
Consolidate components #2169
Conversation
7e6fc79
to
4209e2d
Compare
3de652f
to
1781fa5
Compare
4209e2d
to
8ea5f9f
Compare
1781fa5
to
c38401f
Compare
8ea5f9f
to
eecaaa2
Compare
c38401f
to
d1ad6df
Compare
@JonasVautherin and @ThomasDebrunner I'm thinking of changing the API to require a default, so from:
to:
What do you think? And should it be a breaking change or deprecation notice if you use it without constructor? Related to #2125. |
For me it is fine to completely remove the default and make the build fail if no value is passed. It's fine because it will be a major update, and it's very easy to fix ("oh, it now requires an argument"). Also it's good to make it explicit since apparently some people got confused by the fact that MAVSDK may behave as a ground station by default. |
d1ad6df
to
e767e7a
Compare
This is an attempt to avoid spurious segfaults happening in some of the CI tests for some of the system tests. Presumably they happen on the quick destruction of the objects right after construction. Signed-off-by: Julian Oes <[email protected]>
This should make dealing with the configuration and components a bit clearer. Signed-off-by: Julian Oes <[email protected]>
Signed-off-by: Julian Oes <[email protected]>
e767e7a
to
7e30cfb
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.
Nice! 🚀
This should make dealing with the configuration and components a bit clearer.
This is the last step towards v2 🤞.
Closes #2125.