Skip to content
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

[libconnman-qt] Clarify getTechnology() API dangers. JB#59734 #16

Merged
merged 1 commit into from Jan 31, 2023

Conversation

pvuorela
Copy link
Contributor

@pvuorela pvuorela commented Jan 2, 2023

More or less unused API for which the implementation didn't specify ownership to c++. Then with both qml and c++ deleting content without telling others it's been a problem just waiting to arise.

Instead providing now a simpler hasTechnology(string).

The NetworkTechnology can be instantiated also directly, which is the common usage.

@mlehtima @LaakkonenJussi

@pvuorela
Copy link
Contributor Author

pvuorela commented Jan 2, 2023

Then realized that of course the instances are parented so qml doesn't mess up with those. But on Sailfish this is practically unused so maybe cleaner if we get rid of this way of creating technology instances.

@pvuorela pvuorela changed the title [libconnman-qt] Remove NetworkManager:getTechnology() from qml api. JB#59734 [libconnman-qt] Warn on NetworkManager:getTechnology() dangers. JB#59734 Jan 31, 2023
@pvuorela pvuorela changed the title [libconnman-qt] Warn on NetworkManager:getTechnology() dangers. JB#59734 [libconnman-qt] Clarify getTechnology() API dangers. JB#59734 Jan 31, 2023
@pvuorela pvuorela merged commit b72e0c7 into master Jan 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants