The state for field values lives in the Form component but is rendered and changed in the Field component. How can the Form component share its state with the Field component when Form doesn't directly reference Field? Well, we could use a React context.
- Title Page
- Copyright and Credits
- Dedication
- About Packt
- Contributors
- Preface
- Section 1: Getting Started
- Understanding the ASP.NET Core React Template
- Creating Decoupled React and ASP.NET Core Apps
- Section 2: Building a Frontend with React and TypeScript
- Getting Started with React and TypeScript
- Routing with React Router
- Working with Forms
- Managing State with Redux
- Section 3: Building an ASP.NET Core Backend
- Interacting with the Database with Dapper
- Technical requirements
- Implementing the database
- Understanding what Dapper is and its benefits
- Installing and configuring Dapper
- Reading data using Dapper
- Creating the repository class
- Creating a repository method to get questions
- Creating a repository method to get questions by a search
- Creating a repository method to get unanswered questions 
- Creating a repository method to get a single question
- Creating a repository method to check whether a question exists
- Creating a repository method to get an answer
- Writing data using Dapper
- Managing migrations using DbUp
- Summary
- Questions
- Further reading
- Creating REST API Endpoints
- Technical requirements
- Creating an API controller
- Creating controller action methods
- Creating an action method for getting questions
- Extending the GetQuestions action method for searching
- Creating an action method for getting unanswered questions
- Creating an action method for getting a single question
- Creating an action method for posting a question
- Creating an action method for updating a question
- Creating an action method for deleting a question
- Creating an action method for posting an answer
- Adding model validation
- Removing unnecessary request fields
- Summary
- Questions
- Further reading
- Creating a Real-Time API with SignalR
- Improving Performance and Scalability
- Securing the Backend
- Interacting with RESTful APIs
- Technical requirements
- Using fetch to interact with unauthenticated REST API endpoints
- Interacting with Auth0 from the frontend
- Installing the Auth0 JavaScript client
- Recapping the sign-in and sign-out flow
- Creating the sign-in and sign-out routes
- Implementing a central authentication context
- Implementing the sign-in process
- Implementing the sign-out process
- Configuring Auth0 settings in our frontend
- Testing the sign-in and sign-out processes
- Controlling authenticated options
- Using fetch to interact with authenticated REST API endpoints
- Stopping a data state being set if the user navigates away from the page
- Summary
- Questions
- Further reading
- Section 4: Moving into Production
- Adding Automated Tests
- Configuring and Deploying to Azure
- Implementing CI and CD with Azure DevOps
- Assessments
- Answers
- Chapter 1 – Understanding the ASP.NET Core React Template
- Chapter 2 – Creating Decoupled React and ASP.NET Core Apps
- Chapter 3 – Getting Started with React and TypeScript
- Chapter 4 – Routing with React Router
- Chapter 5 – Working with Forms
- Chapter 6 – Managing State with Redux
- Chapter 7 – Interacting with the Database with Dapper
- Chapter 8 – Creating REST API Endpoints
- Chapter 9 – Creating a Real-Time API with SignalR
- Chapter 10 – Improving Performance and Scalability
- Chapter 11 – Securing the Backend
- Chapter 12 – Interacting with RESTful APIs
- Chapter 13 – Adding Automated Tests
- Chapter 14 – Configuring and Deploying to Azure
- Chapter 15 – Implementing CI and CD with Azure DevOps
- Answers
- Other Books You May Enjoy
Sharing state with a React context
-
No Comment
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.