Fix maxLength broken on files with no extension #30
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.
Currently, files with no extension are not accounted for when satisfying
maxLength
, which results in them not being trimmed at all (accident oflastIndexOf()
returning-1
).This PR fixes it.
BUT! There is another thing which I personally consider an issue. Currently,
maxLength
trims only the filename part to the desired length, and then attaches the extension. I haven't changed this behavior in this PR, but I personally don't consider it right. If I want a filename to be 100 chars long, then it should be 100 chars long including the extension, not 100 chars + extension length.Should I fix this too? And if so, what would be the behavior if it can't be satisfied due to the extension itself being longer than the
maxLength
requirement?The options are:
maxLength
, breaks something else potentially.maxLength
can't be satisfied without breaking something, but this will bite people in the ass, as this is one of those things that tends to happen only in production.