noeldemartin / ramen

Can you make Ramen? Let's find out!

🍜 Ramen

Can you make Ramen? Let's find out!

What is this?

This is a simple (and silly) Solid App that I've created to test interacting with different Solid environments. In theory, a Solid App should work with any backend conforming to the specs. But in practice, there are some things that don't work exactly the same everywhere. It's also a good place to start if you want to learn how I build my apps.

What the application actually does is that once you're logged in, it checks if you have a schema:Recipe container and finds a recipe with "ramen" in the title. If they don't exist, it lets you create them.

This repository should be my golden standard for app interactions with Solid servers, so if anything is not working for you, please let me know! Chances are that it's also affecting my other apps.

Current Status and Known Issues

The application has been tested with the following implementations:

Solid Server	Status	Last tested	Comments
TrinPod	👍 Working	30/01/2024
NSS 5.7.7	👍 Working	08/12/2023
CSS 7.0.1	👍 Working	08/12/2023
ESS	👍 Working	08/12/2023
use.id	⛔ Not working	08/12/2023	The server doesn't expose any writable profiles (nor extended profiles), so the app fails trying to create a type index.
PHP Solid Server	⚠️ Partially working	28/12/2020	The server requires multiple fixes to work properly, reported here: pdsinterop/php-solid-server#42.

Missing a server? Let me know!

ramen's Issues

Unable to create Cookbook

Hi,
I thought I play a little with this gem of an app - but I ran into the following problem...

Using NSS (solidweb.org), I logged in and tried to create a cookbook.
(Using CSS, I could not even login because there is no typeIndex by default, which I assume the app relies on... different issue, I guess...)

Upon creating a cookbook, I get a 500 Server Error:
Dev tools network tab shows a GET request with 404 response to /cookbook/, makes sense, does not exist yet.
Then, a PATCH request to /cookbook/ resulting in the 500. I do not know if NSS changed behaviour for PATCH on non-existent resources.

Thought, I'd let you know. :)

Login form

Hi @NoelDeMartin .
I think you should change login form :
You fill the value with 'https' so the placeholder does not appear and we don't know if we should fill with webid or provider url . I first fill with my webid.
When we clear the login form, the placeholder is too long and we don't even know what we have to type see pic.
I think you should only put 'your identity provider' as placeholder. Or use a select as I do in https://scenaristeur.github.io/verse

Login component here https://github.com/scenaristeur/verse/blob/main/src/components/Login.vue