1.52.1 (April 12, 2023)

Chris Coleman
Chris Coleman Administrator


πŸ€– New Feature - Metadata API

The Metadata API is currently in beta and is the next evolution of the Developer API. It provides support to programmatically manage your Xano content, such as creating new tables and updating schema, as well as a standardized set of APIs for basic CRUD operations. We are super excited to finally have this available, and look forward to enhancing the Metadata API functionality to work with all aspects of your Xano back-end. For more information, see the Metadata API documentation.

πŸ“‘ Database Improvements

Complete Table Export

Export an entire database table to CSV β€” no more using the function stack or checking boxes next to individual records! This supports any number of records, and also supports respecting the applied filters, sorts, and / or database views.

Better Drag & Drop and File Upload

We've made a few improvements to the file upload flow from the database view. This includes the ability to drag files to any cell even without being selected as well as a progress bar for each file upload.

Better Copy / Paste Support in Database View

You can now paste into a cell without being in edit mode.

Better Array Re-ordering Experience

Adjust the order of records within arrays in the spreadsheet view.

⏲️ Timeout Support in Lambdas

No more infinite loops! The default for a Lambda timeout is 10 seconds, but can be changed.

πŸ’Ώ More Data Sources!

You now have the option to add as many additional data sources as you would like. No more "live" and "test" only. This is a premium add-on.

βš™οΈ New Instance Panel

Click the gear icon next to your instance to access all related settings, including the new Metadata API.

New Filters: min / max

Use these to quickly compare two values and find the minimum or maximum. Can be used in compliment with array_min and array_max to compare two sets of values.

🐞 Bug Fixes

Swagger documentation was not always properly identifying required fields

Certain public keys were not woring properly when decoding a JWS token using the RS256 algorithm (thank you, @Ray Deck)