Skip to content

Conversation

@infeo
Copy link
Member

@infeo infeo commented Dec 15, 2021

This closes #121.

It adds two additional results to the shortend health check:

@infeo infeo requested a review from overheadhunter December 15, 2021 11:22
@infeo infeo self-assigned this Dec 15, 2021
@infeo infeo changed the base branch from main to develop December 15, 2021 11:30
@infeo infeo changed the title Hotfix/121 do not add nullbytes Feature: Do not add nullbytes when persisting Long Filename Dec 15, 2021
Copy link
Member

@overheadhunter overheadhunter left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe we can broaden this fix for further unprintable chars. And simplify the check. And rename some methods. 😉

… so split string at that position, check before for base64url and after for any byte

* adjust check, results and unit tests
* add doc
@infeo infeo requested a review from overheadhunter December 16, 2021 11:17
Copy link
Member

@overheadhunter overheadhunter left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a suggestion, but I'm fine to merge it as is.

@sonarqubecloud
Copy link

SonarCloud Quality Gate failed.    Quality Gate failed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

0.0% 0.0% Coverage
0.0% 0.0% Duplication

@infeo infeo merged commit a3ac1a8 into develop Dec 16, 2021
@infeo infeo deleted the hotfix/121-do-not-add-nullbytes branch December 16, 2021 12:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Long filesnames are persisted with NULL Bytes at the end

3 participants