-
Overcoming Challenges in Building an API with RTK Query
Building an API with RTK Query can be a rewarding experience, but it comes with its own set of challenges. One common hurdle is managing large apiSlice files, which can become difficult to maintain as the number of endpoints grows. To address this, I explored code splitting and modularizing endpoints, but these approaches introduced their… Read More
-
REST API Paths
When naming REST API paths, it’s important to follow best practices such as avoiding file extensions, using HTTP verbs like GET, POST, PUT, DELETE, and placing variable names in the path. Proper structuring of endpoints helps differentiate between collections and singletons, like using /api/users for a collection and /api/users/123 for a specific resource. Relationships between… Read More
-
Drag and Drop Reordering with RTK Query and PHP
Today’s work focused on implementing drag and drop functionality, improving error handling, and refining API endpoints. Key features include a new item creation dialog, item reordering, and enhanced error reporting with stack traces. Backend changes involved refactoring API methods, handling server-side item movement, and using appropriate HTTP status codes. Additionally, the frontend was updated with… Read More
-
RTK Query
I transitioned my Redux application to use RTK Query for API calls. This reduced the need for selectors and simplified data management. While RTK Query is powerful, it has limitations like needing many endpoints for a single server and requiring complex TypeScript types for builders. Sagas are still used for specific cases like handling drag-and-drop… Read More
-
Queue Downloads
I created @codejamboree/web-requests-queue, a library that queues and spaces out HTTP requests to prevent server overload, with features like pausing, resuming, and downloading files or parsing JSON. I also developed a basic testing platform with function mocks and expectations. The library is available on GitHub and npm. Read More
-
Separating Services
Changes were made to store the secrets in a separate database rather than a JSON file to allow scalability and portability. An initial design had setup an over-engineered system for an enterprise. Then it was simplified, and further normalized. Read More