• Introduction
• Setup
• Overview
• 1. Install the CLI
• 2. Create the App
• 3. Run the App
• 4. Setup the API
• Layout
• Overview
• 1. Install Bootstrap
• 2. Add Custom Styles
• 3. Add the Header
• Routing
• Overview
• 1. Convert Title to a Link
• 2. Add Feed to Routes
• Data Structure
• Overview
• 1. Add Mock Data to Feed
• 2. Create Tweet Component
• 3. Add Mock User Data
• Fetching Data
• Overview
• 1. Set API Location
• 2. Create Tweet Model
• Convention over Configuration
• 3. Connect Feed Component
• 4. Display Loading Message
• 5. Fetch User for Tweet
• Authentication
• Overview
• 1. Add Profile to Layout
• 2. Add Auth0 Config
• 3. Add Login Page
• 4. Redirect to Login
• 5. Add Callback Route
• 6. Add Logout Page
• 7. Fetch Current User
• 8. Save User to Context
• Server
• Overview
• 1. Clone the API Server
• 2. Parse the Collection
• 3. Parse the Model
• 4. Add Unauthorized Experience
• 5. Add Authorization Header
• Pagination
• Overview
• 1. Add Pagination Metadata
• 2. Paginate the Tweets
• 3. Add Pagination Links
• 4. Improve User Experience
• Infinite Scrolling
• Overview
• 1. Create Load More Button
• 2. Create Infinite Scrolling List
• 3. Convert the Feed
• Cleanup
• Overview
• 1. Remove Unnecessary Code
• Dialogs
• Overview
• 1. Add Create Button
• 2. Mounting Dialogs
• 3. Add Create Dialog
• 4. Simplify the Dialog
• 5. Generate Dialog via Hook
• 6. Add Edit Dialog
• 7. Add Delete Dialog
• Authorization
• Overview
• 1. Hide Edit Link
• 2. Hide Delete Link
• 3. Alternative Approach
• Optimistic Updates
• Overview
• 1. Freeze Pagination Data
• 2. Display New Tweets
• 3. Display Optimistic Tweets
• 4. Add Optimistic Values
• 5. Show Optimistic Visual Cues
• 6. Hide Deleted Tweets
• Normalization
• Overview
• 1. Normalize Tweet Response
• Filtering
• Overview
• 1. Add Filter
• 2. Display User Tweets
• WebSockets
• Overview
• 1. Add WebSocket Support
• 2. Send Client ID to API
• Publishing
• Overview
• 1. Create Production Build
• 2. Deploy to Production
• 3. Create Production Config
• 2. Redeploy to Production
• Next Steps
• Overview
• Misc
• Installing Node
• Completed Project

Step 2: Create a Tweet Model

In this step we're going to create a model for our tweet, and in the process, we'll learn about some of the functionality automatically provided by Lore as a result.

You can view the finished code for this step by checking out the fetching.2 branch of the completed project.

Create a Tweet Model

Before you can fetch data in Lore, you first need to create a model that represents the resource you want to fetch. Since we want to fetch tweets, we're going to create a tweet model.

Run this command to generate that model:

lore generate model tweet

This will create a model called tweet, and place the file at src/models/tweet.js.

You can learn more about the generate model command here.

Similar to the files in the /config folder, this file contains a lot of comments, which document the properties you can change, along with their default values. But if you ignore all the comments, this file is essentially empty:

// src/models/tweet.js
export default {

};

While it may not look like it, we now have all the code required to fetch tweets from the API, and we'll explore some of that functionality in the next step.

Visual Check-in

If everything went well, your application should now look like this. Still the same as before :)

Code Changes

Below is a list of files modified during this step.

src/models/tweet.js

export default {

};

export default {

}

export default {

}

Next Steps

Next we're going to talk about a design paradigm called convention over configuration, and introduce some of the functionality we just unlocked.