Is there any functional differences between using the built in Xano plugin vs. just using the REST API plugin?
Check it out. It brings in your endpoints and their required parameters so you don’t have to think about importing all that to the api connector plugin. It also handles the auth portion of xano very nicely.
Those are just UX differences though right? Not functional differences in capabilities, right?
Isn’t the auth portion a separate Xano Auth plugin?
Sorry, yes. You’re right. Those are different.
In practice, you won’t notice much difference with the exception that when you use the xano auth plugin with the db plugin the auth plugin automatically sends auth credentials of your logged in user for your xano calls. Otherwise you’d just throw the tokens in the header of your api calls.
Technically, the Xano Plugin is a layer of abstraction on top of the REST API plugin. As @jaredgibb said, it automatically sends the user token when you’re using the Xano Auth plugin as well.
The Xano Plugin doesn’t handle custom headers for now, so you’ll need to use the REST API plugin. But we’ll add this to the Xano plugin soon!
Hey @Quentin, is there any ETA on this by chance?
I’m really excited about it, as I feel like it’s the last barrier to truly being able to have a useful staging environment with Xano outside of defaulting to the REST API plugin.
For what it’s worth, it looks like there is progress here based on GitHub activity