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

settings: Do not export without implementations #1552

Merged
merged 1 commit into from
Jan 9, 2025

Conversation

kleifgch
Copy link
Contributor

@kleifgch kleifgch commented Dec 29, 2024

If no settings portal implementations are found, the settings_create() function currently returns NULL and the No skeleton to export warning is emitted. This change guards against that, which is more consistent with the other portals.

@swick
Copy link
Contributor

swick commented Jan 7, 2025

Might make sense to always export the settings portal even if there are no backends.

@swick
Copy link
Contributor

swick commented Jan 8, 2025

Having the settings portal exposed and returning nothing at all doesn't get us anything, so I'm now in favor of this change.

This LGTM with the nit resolved.

If no settings portal implementations are found, the `settings_create()`
function currently returns NULL and the `No skeleton to export` warning.
This change guards against that, which is more consistent with the other
portals.
@kleifgch kleifgch force-pushed the fix-filename-warning branch from 30f15c5 to 09edad5 Compare January 9, 2025 07:43
@kleifgch kleifgch requested a review from swick January 9, 2025 07:48
@smcv smcv added this pull request to the merge queue Jan 9, 2025
Merged via the queue into flatpak:main with commit 34ff12c Jan 9, 2025
5 checks passed
@kleifgch kleifgch deleted the fix-filename-warning branch January 10, 2025 05:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Triaged
Development

Successfully merging this pull request may close these issues.

3 participants