The previous chapters covered the system administration topics from the storage, networking, and security domains. This chapter introduces the container engine that the LFCS exam lists under “Operations Deployment”: Docker. The exam tests the conceptual model: the client-server architecture, the three core objects (image, container, registry), and the difference between containers and virtual machines. The…
The previous chapters covered the backup strategies and the tools that create the backups: tar and rsync. This chapter covers the step that determines whether the backups are worth anything: the testing. A backup that has never been restored is a backup that might not work. The LFCS exam tests the conceptual model: the distinction…
The previous chapter covered the data loaders that fetch the route data before the component renders. This chapter covers the UI that appears while the loader is in progress. In the TanStack Router, the pending state is managed at the route level, not the component level. The route object has a pendingComponent property that renders…
The previous chapters covered the path and search parameters: the URL data that the route reads. This chapter covers the data loaders: the functions that fetch the data before the route component renders. In the React Router Data mode, the loader is defined in the route object with the loader property. In TanStack Router, the…
The previous chapter covered the path parameters, which are part of the resource identity. This chapter covers the search parameters: the key-value pairs in the query string that configure the view. The TanStack Router’s search parameter handling is fundamentally different from the React Router’s. The React Router returns the raw URLSearchParams object, and the component…
The previous chapter covered imperative navigation with the useNavigate hook, which is fully typed against the route tree. This chapter covers the path parameters: the dynamic segments that allow a single route file to serve multiple URLs. The TanStack Router’s handling of the path parameters is stricter than the React Router’s. The parameter is declared…
The previous chapter covered the <Link> component, which is the declarative navigation mechanism. This chapter covers the imperative navigation: the useNavigate hook, which returns a function that navigates programmatically. The LFCS exam does not test TanStack Router, but the front-end engineering certification paths do. The critical distinction is between the typed useNavigate hook and the…
The previous chapter covered the <Link> and <NavLink> components, which are the declarative navigation mechanisms. This chapter covers the imperative navigation: the useNavigate hook, which returns a function that programmatically navigates to a route. The LFCS exam does not test React Router, but the front-end engineering certification paths do. The critical distinction is between the…
The previous chapters covered the flat route configuration and the navigation links. This chapter covers the nested route structure: the route tree where a parent route renders a shared layout and the child routes render inside it via the <Outlet /> component. The LFCS exam does not test React Router, but front-end engineering certification paths…
The previous chapter covered path parameters: the dynamic segments in the URL path that identify a resource (/users/:id). This chapter covers query parameters: the key-value pairs in the URL search string that configure the view (?sort=name&page=2). The LFCS exam does not test React Router, but front-end engineering certification paths do. The critical distinction is between…