Let’s talk about why we want an API for this component. Some of the reasons include:
- Developers using the Data Store do not need to know the implementation. They don’t need to know if it’s built in OOP, static class, or procedural. Rather, the API wires to the Data Store. It hides away the implementation, exposing public facing procedural functions to interact with it.
- Future proofs your work.
- Makes it easier to work with the Data Store.
If you listen carefully, you can hear the 1s and 0s flowing in your computer.
Total Lab Runtime: 02:39:26
- 1 Planning Introductionfree 02:50
- 2 What is a Data Store?free 03:51
- 3 Defining the Basics of a Data Storepro 09:19
- 4 Document the Basicspro 14:06
- 5 Simulate Store and Getpro 08:46
- 6 Identifying Items in the Storepro 17:07
- 7 Defining the Container: Data Type & Retainpro 16:48
- 8 Reviewfree 05:05
- 9 Feature: Check if Item Exists in Storepro 04:44
- 10 Feature: Remove an Item From the Storepro 06:53
- 11 Feature: Replace an Item in the Storepro 11:29
- 12 Feature: Merge with (Add To) Existing Itempro 10:33
- 13 Feature: Empty the Data Storepro 05:34
- 14 The Need for an APIpro 09:16
- 15 Document the API Basicspro 14:52
- 16 Global, But Controlled Accesspro 07:49
- 17 Push to GitHub, PR, Merge, & Syncpro 08:01
- 18 Wrap it Upfree 02:23