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

XdpAppInfo refactoring, Part 3 #1411

Merged
merged 3 commits into from
Oct 4, 2024

Conversation

swick
Copy link
Contributor

@swick swick commented Aug 6, 2024

This is a continuation of #1369.

@swick swick force-pushed the wip/xdp-app-info-part3 branch 2 times, most recently from ea9d446 to a435003 Compare September 14, 2024 15:17
@swick
Copy link
Contributor Author

swick commented Sep 14, 2024

Rebased the last few commits of the XdpAppInfo refactoring on part 2.

@swick
Copy link
Contributor Author

swick commented Oct 4, 2024

Gentle ping. This one should be pretty straight forward.

For example, for flatpak, the sub-app-id must be a valid app id in
itself and also have the app-id as a prefix, with a dot as separator.
Host apps don't have any restrictions.

The flatpak_is_valid_name function has been copied from the flatpak
project.
For flatpak apps, the dynamic launcher desktop file id shall be a valid
flatpak id plus the .desktop part.

Use the newly introduced xdp_app_info_is_valid_sub_app_id function to
make sure this is the case and allow other app kinds to add similar
restrictions.
@GeorgesStavracas GeorgesStavracas added this pull request to the merge queue Oct 4, 2024
@GeorgesStavracas GeorgesStavracas added this to the 1.20 milestone Oct 4, 2024
Merged via the queue into flatpak:main with commit f268436 Oct 4, 2024
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Triaged
Development

Successfully merging this pull request may close these issues.

2 participants