brazerzkidaiuk.blogg.se

Xsection app update#

Xsection app update#

We add a new field to the table representing a workout in the schema file, and run prisma's migration tool to update the local database with the new field.

I've done my best to tell a story in the PR associated with this work. I've been thinking of these abstractions like a diagram of Earth's core, with the database at the center and the UI on the outside: Redwood ties these all together to give you a GraphQL endpoint with access to your database.

The back-end is supported by a database schema definition file, GraphQL schema definition files, and services for handling data interaction and business logic.

The Empty, Loading, Error, and Success states of the component, based on data loaded from the GraphQL endpoint.

The queries/mutations it will send to the GraphQL endpoint.

Within each Cell, you specify a few things:.

When you want to interact with your GraphQL back-end from your React front-end, you render a Cell component.

The Redwood Page construct represents a page that a user can hit in your React app.

You don't need to set any of this up.Redwood's CLI takes care of it for you.

A Redwood app consists of a React front-end and a GraphQL API back-end.

Here are some things to know about Redwood:

The PR we'll look at adds a single field - isKeyWorkout - to the PlanWorkout model, and propagates it up the entire stack, from database to UI. One thing that's missing - is the workout a key workout? Is it the race I'm working up to? Is it maybe not a race, but a workout I'm really interested in crushing, like an FTP test? I like to see these workouts on my grid, so I know when they're coming up. So far a PlanWorkout tracks things like activity (running, biking, etc.), target miles and/or duration, and intention for the workout (recovery, race, etc.). My database model has an entity that represents each workout I want to get in. Nothing too complicated - I want to track my scheduled workouts, my actual workouts, and get a sense for whether I'm on-target with my training. I'm starting to ramp up my training for this year, and I decided I want an app for tracking it this time. It's worked fine, but are we even web developers if we're not turning spreadsheets into web apps? Some background about my appįor the last few years I've tracked my running/triathlon training plans with a spreadsheet. In this article I'll give you a little background on the app I'm building and some fundamental Redwood concepts, and then we'll take a look at one of my recent PRs to see the cross-section of a Redwood app. I've been embracing pull requests as a means to tell stories on this personal project, and I noticed that some of my PRs show a nice cross-section of all the Redwood abstractions from the UI to the database. I recently started building a training journal app with Redwood. It allows me to focus on building features instead of worrying about infrastructure and setup. While I might not agree with all of Redwood's opinions, I'm perfectly happy to accept them for the sake of shipping things. It puts opinions around all the decisions you need to make to build a React app, and abstractions around the most common features you need to make the app usable. Cross-Section Of A Redwood App Published Apby Steven Hicks