-
-
Notifications
You must be signed in to change notification settings - Fork 375
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
Minor syntax bug when using quotes in the app's name #1876
Minor syntax bug when using quotes in the app's name #1876
Comments
Thanks for the report. This is a class of problem we've been slowly squashing over time; See #905, #1746, and some others. If you're interested in trying your hand at fixing this, the history and linked issues for #1746 are a good point of comparison. The fix for this comes in 2 parts. The first part is that we need to modify the briefcase-android-gradle-template so that anywhere user-generated content is inserted, it is appropriately escaped. The second part is that we need an appropriate escape filter. We have escaping filters for XML, TOML and PLIST; we clearly need one for gradle as well. This will likely be structurally similar to the It would also be worth auditing all the other places that user-generated content is being inserted. Based on a quick inspection, it looks like an app with a formal name or app name that contains |
Keen to grab this one. |
Please do - I'm around all tomorrow if you want to discuss any details! EDIT: I'm around ... at the PyCon AU sprints. |
Describe the bug
I've just noticed that if you create an app and include a quote in the name (
'
),briefcase
does not escape it inside thesettings.gradle
file. Nothing very concerning, just a bit misleading for people who may not know about this kinda stuffSteps to reproduce
briefcase
'
inside the name, e.g. "John Doe's amazing application"Why does writing this feel like greentext?
Expected behavior
I expected it to compile without errors. lol
Screenshots
No response
Environment
Like, are these really needed?
Logs
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: