Build: sanitize and validate ApplicationIdentifier as a Java package name
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 77/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- csharp
- Domain
- build-system
Research direction
Start at ProjectBootstrapper.cs:61, where PlayerSettings.ApplicationIdentifier is set, and trace the export validation entry point and existing unit test conventions. Add coverage for hyphens, spaces, leading digits, Java keywords, and non-ASCII input. Done means bootstrap sanitizes identifiers, export reports invalid identifiers in existing projects without silently rewriting them, and the tests pass.
Written by the indexing model from the issue text.
Description
Current State
ProjectBootstrapper.cs:61 sets PlayerSettings.ApplicationIdentifier to com.turian.<title> unsanitized. Android needs a valid Java package: two or more segments, each [a-zA-Z][a-zA-Z0-9_]*, no Java keywords.
Tasks
- Sanitize at bootstrap
- Validate on export with a clear error
- Unit tests: hyphens, spaces, leading digits, keywords, non-ASCII
Acceptance Criteria
- Tests pass; existing projects with invalid ids get a validation message, not a silent rewrite
Related
- Android plan task A14 · seniority Jr · mergeable now (.NET 10)
- Platform roadmap: #100
- Dominant language
- C#
- Stars
- 1
- Forks
- 1
- Avg merge
- 1h 34m
- Merged PRs (30d)
- 35
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from MASS4ORG/Turian
-
c:assets p:low size:XS t:task
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
c:build c:editor p:medium size:XL t:feature
Difficulty 5/5 Over a week Newbie friendliness 5/100
Maintainers usually reply within 1 day
-
c:build p:medium size:XL t:refactor
Difficulty 5/5 Over a week Newbie friendliness 8/100
Maintainers usually reply within 1 day
-
c:build c:ui p:low size:L t:refactor
Difficulty 5/5 Over a week Newbie friendliness 15/100
Maintainers usually reply within 1 day
-
c:assets c:build p:low size:S t:refactor
Difficulty 5/5 Over a week Newbie friendliness 15/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 7 days
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
vchelaru/FlatRedBall2#1481 ·
Maintainers usually reply within 1 day
-
ai-chat bug trivial
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
area-signalr
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
dotnet/aspnetcore#69842 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day