mathiastj/recipes_frontend

Deprecated after Heroku shut down their free tier. Replaced by: https://github.com/mathiastj/recipes-frontend which uses supabase as the backend

Recipes Frontend

My personal cooking recipes, not publicly available.

Motivation

Keeping track of cooking recipes and easily searching for titles and ingredients instead of leafing through a book.

Technical motivation

• Wanted to try out Hasura and React Admin.
• See how quick it was to spin up a new CRUD app.

The project is using Hasura hosted on a free Heroku dyno.
https://github.com/Steams/ra-data-hasura-graphql is used as a data provider to connect the Hasura backend to the React Admin frontend.

recipes_frontend's Issues

Add category

As a field in recipes
Make it a foreign key so categories can be edited too?

Very ugly auth

Authentication and authorization is very ugly since I don't have an auth service.

I'm using 'x-hasura-admin-secret' directly, and I enter this as a password on login.

I've used a few hacks to create a dataProvider before login and switch after login:

• Create a bogus dataProvider preAuthDataProvider. This causes a warning to be shown on the login page due to it not living up to the spec completely.
• Force the page to refresh in the authProvider upon login, so that I can switch the data provider to the actual one now that I have the secret to authorize with.

Trying to call the hasura backend without the secret or with a wrong secret causes react admin to throw a hard error and makes the site unusable.

There's also no protection setup against XSS.

login is broken with the new data provider

data provider not reset on login

Add number of persons