After quite a lot of work, the Hubleto team finally merged refactoring of Hubleto's React UI into functional components.
This is more than just another merged branch. It is one of the bigger changes made to the Hubleto codebase so far: the React UI has been moved from class-based components to functional components.
Why did the they do it?
Hubleto has been around for a while, and a lot of its UI was originally built using React class components. They worked, but React has changed quite a lot since then.
Today, functional components and Hooks are the standard way of building React applications. They generally require less boilerplate, make components easier to compose, and provide a much cleaner foundation for further development.
So the goal of the refactoring was not simply to "replace classes with functions". The Hubleto team wanted to use the opportunity to clean up parts of the UI, remove some legacy patterns, and make the code easier to understand and maintain.
Of course, a refactoring of this size is not just about changing syntax. A lot of existing components depend on each other, and changing something in one place can easily affect something somewhere else.
That was probably one of the main challenges of this work: keeping the existing functionality working while changing a significant part of the underlying implementation.
A practical example: the new Form component
A good way to see what the new functional approach looks like in practice is the new Hubleto Form component. This article includes a concrete example of the new functional-based form architecture. It gives developers a better idea of how the refactored React UI is intended to look and how the new architecture can be used when building Hubleto applications.
What's next?
The UI refactoring is only one part of Hubleto 2. One of the areas the Hubleto team wants to focus on next is integration.
ERP and CRM applications rarely work on their own. In a real business environment, Hubleto needs to communicate with payment providers, communication tools, cloud services, marketing platforms and many other systems.
The Hubleto team therefore wants to continue improving the way Hubleto connects to external services, including its webhook architecture, API connectors and native integrations.
The idea is simple: Hubleto should fit into the existing technology stack instead of forcing businesses to work around it.
For the Hubleto team, this refactoring is an important foundation for what comes next. There is still a lot to do before Hubleto 2 is finished, but having the React UI modernized provides a much better base for further development. And since Hubleto is open source, anyone can follow the development, explore the code and try the new functional React UI.
The first Hubleto 2 Alpha release is getting close.
Top comments (0)