-
-
Notifications
You must be signed in to change notification settings - Fork 263
Sanitize attachment filenames before saving so they are acceptable by QFieldCloud #6197
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
Merged
Conversation
This file contains hidden or 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
Sentry Issue: QFIELDCLOUD-2YD |
0c5364c
to
c6dfe7f
Compare
🎉 Ta-daaa, freshly created APKs are available for d423855: arm64-android |
c6dfe7f
to
0d86867
Compare
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.
clang-tidy made some suggestions
… QFieldCloud QFieldCloud recently added a restriction for file names so they can work on all popular operating systems. However, the attachment naming expressions have no restrictions to what they are going to evaluate. Therefore the new `FileUtils::sanitizeFilePath` function has been added that will convert the disallowed chars into underscores and return an empty string when the file path cannot be fixed, for example when it is too long. If an empty string is returned,then the default naming kicks in to guarantee the filename can be saved and can be uploaded to QFieldCloud.
d30a86d
to
d423855
Compare
@nirvn finally ready for a review. |
nirvn
approved these changes
May 1, 2025
Let's merge that and get our ~3,000 unstable user to stress test it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
QFieldCloud recently added a restriction for file names so they can work on all popular operating systems. However, the attachment naming expressions have no restrictions to what they are going to evaluate.
Therefore the new
FileUtils::sanitizeFilePath
function has been added that will convert the disallowed chars into underscores and return an empty string when the file path cannot be fixed, for example when it is too long.If an empty string is returned,then the default naming kicks in to guarantee the filename can be saved and can be uploaded to QFieldCloud.
QFieldSync config:


Resulting values: