-
Notifications
You must be signed in to change notification settings - Fork 117
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
validator: Add some limited developer-ID validation
- Loading branch information
Showing
2 changed files
with
31 additions
and
3 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
faa48f6
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.
Can this be added to the demotion allowlist, please?
faa48f6
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.
…and on an unrelated note, I wouldn't mind if
description-has-plaintext-url
could also be demoted. I can submit PRs for both.faa48f6
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.
Why would you want to do that? Both are "must not" wordings in the specification. If there are false-positives, we should fix the validator instead...
faa48f6
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.
It's a breaking change. We cannot be breaking builds for developers forever. We will need to find apps which will explode on that, report issues, and announce a reasonable cut-off date.
faa48f6
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.
As for the URL because it's already used in the wild to point users to documentation not fitting existing types, usually when users is expected to do something on the host for the app to work properly, or purchase assets from a game store.
faa48f6
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.
It's not though - this will not trigger unless you actually have a developer tag, so if you have developer_name, you'll be fine. It will become a huge issue though if we do not validate this according to spec immediately, because then people will do whatever and we will make them fail validation later once the check is added. Furthermore, the spec is clear on this, and so are the Flathub guidelines - follow them, and you're safe.
In addition, I ran this against thousands of metainfo files overnight (general compose and generator run, also for a different test) and this tag was emitted exactly 0 times.
As for the URL thing: It will result in a plain, unclickable URL in the description text, which is ugly and usually not the intent of the application author. It also, from experience, annoys designers very much. If I relax this check, I'll have bug reports about adding it back within a week, I guarantee it.
So, we either add a proper
<url/>
style element to descriptions to address this properly, or we don't and people add URLs to the appropriate place (withinurl
blocks) and reference them from the text.