search

inrupt / solid-client-js

Library for accessing data and managing permissions on data stored in a Solid Pod
https://docs.inrupt.com/developer-tools/javascript/client-libraries/
MIT License
230 stars 37 forks source link

Can't preview markdown file in Penny as they get `text/turle` type instead of `text/plain` #2336

Open thhck opened 7 months ago

thhck commented 7 months ago

Search terms you've used

contentType, markdown

Bug description

On the community solid server recipe using Penny UI , text file uploaded as .md .markdown or CSS's by default README.$markdown can't get priviewed by penny. In the debugger I can see they have the text/turtle content type, instead of text/plain ( which I believe is the correct type).

To Reproduce

  1. clone and run CSS penny recipe
  2. Create a new account and a pod
  3. Login
  4. on a shell echo bar > foo.md
  5. upload foo.md to your pod using penny
  6. on penny, open foo.md

Expected result

Penny should preview the file ( "bar" ) as if it was a plain text file ( check the result if you use foo.txt instead of foo.md in step 4 )

Actual result

Penny shows This resource is empty.

Environment

System: OS: Linux 5.15 Fedora Linux 36 (Thirty Six) CPU: (4) x64 Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz Memory: 4.72 GB / 11.39 GB Container: Yes Shell: 5.9 - /home/user/.nix-profile/bin/zsh Binaries: Node: 18.16.1 - ~/.nvm/versions/node/v18.16.1/bin/node npm: 9.5.1 - ~/.nvm/versions/node/v18.16.1/bin/npm pnpm: 8.11.0 - ~/.nvm/versions/node/v18.16.1/bin/pnpm bun: 1.0.15 - ~/.bun/bin/bun Browsers: Chrome: 121.0.6167.184 Chromium: 111.0.5563.64 npmGlobalPackages: corepack: 0.17.0 create-preact-app: 0.2.0 date-prompt: 1.0.0 eas-cli: 7.1.2 expo-cli: 6.3.10 npm: 9.5.1 pnpm: 8.11.0

Additional information

thhck commented 7 months ago

As suggested by @Vinnl here, it might be an issue with the Solid Community Server and not the solid client

NSeydoux commented 7 months ago

Hi @thhck , thanks for reaching out, and thanks for linking to the upstream issue. Since it is likely the root cause is out of the scope of the library, I will not investigate further until there is evidence CSS is not at fault here :).

But please do update this issue as appropriate when there are news from the CSS team, I'm happy to pick this up if it turns out the libraries are incorrect in some way.