Skip to content
This repository was archived by the owner on Oct 9, 2025. It is now read-only.

Conversation

PhilippS93
Copy link

What kind of change does this PR introduce?

fixes supabase/supabase#18175

What is the current behavior?

Please link any relevant issues here.

What is the new behavior?

Feel free to include screenshots if it includes visual changes.

Additional context

Add any other context or screenshots.

@coveralls
Copy link

Pull Request Test Coverage Report for Build 6531473143

  • 1 of 1 (100.0%) changed or added relevant line in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 91.739%

Totals Coverage Status
Change from base Build 6143028547: 0.0%
Covered Lines: 185
Relevant Lines: 197

💛 - Coveralls

@kamilogorek
Copy link
Member

Related #70

@MariusWilsch
Copy link

Why is nobody pushing this. It's end of 2024 and this is still the same issue!

@cohlar
Copy link

cohlar commented Mar 22, 2025

Why is nobody pushing this. It's end of 2024 and this is still the same issue!

I'm not familiar with the dev decisions, I just know this solution is quite "partial" in the sense there are a lot of file types beyond pdf that would need a similar treatment. e.g. all the .docx, .xlsx, .pptx files (I'm sure that's just the tip of the iceberg).

@mandarini
Copy link
Contributor

moved here: supabase/supabase-js#1757

@mandarini mandarini closed this Oct 9, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Wrong Content-Type return parsing for application/pdf on edge function

6 participants