fix fdroid package name validation#559
Conversation
Greptile SummaryThis PR adds an
Confidence Score: 5/5Safe to merge — the validation is correctly placed before all file I/O and covers the full set of malformed inputs described in the PR. The No files require special attention. Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A["build / ship called"] --> B["assertPackageName(packageName)"]
B --> C{"regex matches?"}
C -- No --> E["throw Error: invalid packageName"]
C -- Yes --> D{"segment in JAVA_RESERVED_WORDS?"}
D -- Yes --> E
D -- No --> F["continue build/ship logic"]
F --> G{"mode?"}
G -- "main-repo" --> H["write metadata YAML or open fdroiddata PR"]
G -- "self-hosted" --> I["fdroid update or publish repo"]
Reviews (2): Last reviewed commit: "address fdroid package name review" | Re-trigger Greptile |
Summary
Why
pkg-fdroid used config.packageName directly in the generated metadata filename. Invalid values such as ../escape or com.acme/app should be rejected instead of influencing the artifact path.
Tests