The last part focused on using observedAttributes() to switch what the main action button did, depending on the current document state. In this part we'll cover the functionality behind the search button and the save.
In the last two parts we created our first web component and converted the login function into services we could use for all data interactions, the first use being to load data for any select controls in the application. Now it's time to create the ship form.
We've got a login and a landing page, we're ready to start building the bulk of the application now. But we need the data. In part six we handled the login, both for a mock session and the actual authentication to Domino REST API. But that format is going to quickly get messy as we build out the rest of the application. We can do better.
We've got a login page, we've got theming, we're handling light mode and dark mode. Now we're ready to start adding our landing page.
In the last part we created the login form. In this part we're going to start adding some theming.