posted by chriskapp on
We like to announce the next version 6.2 of Fusio. The largest change of this release is the backend migration from
Angular 18 to 20. This affects the Angular SDK, TypeSchema editor and backend app, in
the process we have also updated many dependencies like the Monaco
editor and Apexcharts. All components of the backend app are now standalone, and
we use the new @for @if syntax and signals for input and output. This makes the backend app
fit for future Angular releases, and we also benefit from all changes in the ecosystem. Since this is a larger rewrite
of the backend feel free to open an issue in case you have found a
problem. The following list covers all important features of this release:
The backend app was migrated from Angular 18 to 20 using new language features and updating all dependencies.
We have implemented a new code editor view to develop actions.
This view is dedicated to the Worker actions and improves the development experience for users who like to use the backend. The editor has now more space and on the right side panel you can select a connection to get additional information about this connection. While developing an action you often need to use an existing connection i.e. select data from a table or access a remote API. This side panel provides more information like available methods, and we also show details if available, i.e. for a database connection we list available tables on the connection. Besides this we have also improved the code completion of the editor.
To create and update a schema we now use everywhere the schema editor. Previously there was a JSON editor where a user could provide a raw TypeSchema specification but this is now replaced with the editor since it is much easier for new users to create a schema.
We use this editor already in many projects and it helps to improve the user experience. The editor has also an import option so if the user likes to provide a raw TypeSchema specification this is still possible.
At the marketplace we have introduced a new bundle concept. A bundle is basically a set of Fusio entities like i.e. an action or schema. You can create a bundle to share such entities with our community. With this new option you can now create a bundle at your local Fusio installation and submit these entities to the marketplace.
Basically a bundle contains a reference to your local entities and if you submit the bundle to the
marketplace Fusio will convert those references into a fitting object. A third user can then install this bundle
from the marketplace. You need to register
at the marketplace, and then you can provide your credentials at your local Fusio installation under
System / Config (marketplace_client_id / marketplace_client_secret).
This is only a soft launch of this new concept, but in the future users could use this marketplace to create a vibrant community to share such entities. This would work similar to platforms like Zapier where users can share existing actions to solve or automate a specific task but in the open-source and self-hosted spirit.
The body parameter is no longer required.
When normalizing OAuth2 usernames we automatically remove the @ part.
We have added some new statistics to see the request count by ip, operations and user.
Internally we have migrated the Fusio backend implementation and many libraries from Psalm to PHPStan.
If you want to provide some feedback take a look at our GitHub discussions or issues page.
Best regards
Christoph