3 ms·
OT: Funny how this is never the problem I had. I’ve always had trouble with the bits on the screen, not connecting the bits behind it. Every time I see a new pr
by easton 5y ago
OT: Funny how this is never the problem I had. I’ve always had trouble with the bits on the screen, not connecting the bits behind it. Every time I see a new project that says “connect APIs real quick to your frontend” or “one click deploy database table don’t think about backend” I always think “but you’re skipping over the fun part!”
Congrats on the launch, this looks really neat.
- sgrove 5y agoAh, then you're in luck! Down the road, you should be able to tell Netlify Graph how to map the boilerplate-y bits from the API to the screen, so you always get something that works (with your best practices implemented) that you can start tweaking from. We already do this for a handful of frameworks (plain functions, next.js, remix, etc.). Here's a bit of an older example (with a much older UI) of how it works with a very plain project mapping various GraphQL operations to next.js https://youtu.be/0LJr15A0t4Y?t=73 https://youtu.be/0LJr15A0t4Y?t=73, including - client-side forms - server-side form validation - auto-detecting when the user needs to log into a service client-side to do some query/action - prompting the user to log into the service - re-running the query on successful login Basically, you should be able to click around in an API, run a test query, say, "Oh, I want that in my app", then click a button and have it inserted exactly how you and your team would have written it.