Throughout the summer, we released a number of updates to improve our Xano plugins and support the latest Xano features like data sources and branches.
You can now:
In addition, both Xano plugins now support Xano data sources and branches.
In WeWeb, you can now decide to work with different Xano data sources and branches depending on whether you're working:
This is helpful if you want to iterate on your WeWeb app with test data and API calls that are still in editing mode in Xano without breaking your live app.
For example, you could have a "live" data source and a "test" data source in Xano:
In the example below, we chose to work with the data from the "test" data source inside the WeWeb editor, and on the app in staging:
As a result, when working in the WeWeb editor or viewing the app published in staging, the data that is displayed will be the data from the "test" data source in Xano. We will not be able to see or work with the data in the "live" data source.
We can apply the same logic to work with different Xano branches. In the example below, we will test the Xano "v2" branch in the WeWeb editor and the app we publish on the staging environment but the Xano "v1" branch will still be live in our app in production:
Note that Xano data sources and branches are advanced features that may require some time to master if you don't have a developer background. We think the power and flexibility it gives you to build professional web-apps is well worth the trouble though.
Learn more about working with different Xano data sources and branches in WeWeb.
In addition to the new features described above, the team took the opportunity to make some UX improvements and bug fixes related to the Xano plugins:
In the example below, I tried to bind an integer to a field that expects a string in Xano. As a result, I can see an "Expected format" warning: