Repository navigation
fix: proper compound ext support + compression ext handling - #1536
Merged
Merged
Conversation
Co-authored-by: Sola-ris <190788035+Sola-ris@users.noreply.github.com>
This was
linked to
issues
Oct 7, 2026
2 of 8 tasks
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
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.
Summary
This PR fixes #1533 and implements #1534, while porting a bit of #1506 to implement #1505. Files with compound suffixes (currently limited to compression extensions but expandable with future registrations) will now search and display those suffixes as you'd expect as per #1533. All files with these compressed extensions will also now have the ability to render, not just archives, as these extensions are detected and routed through a new decompress function. Bunch of tests added as well.
For an example of the search changes, searching
filetype:tarwill now return.tar,.tar.gz,.tgz, etc., andfiletype:tar.gzwill be more specific and only return.tar.gzand.tgz. Searchingfiletype:gzwill also return anything like.tar.gzor.txt.gz.This was also done with a minimal impact to performance. On the
devbranch I may add an additional column to the db to cache any compound extensions, which would further speed up search performance in this area.Tasks Completed