Xano collection end points - best practice for parsing

[kdjamo]

Hello, when reading a basic collection from Xano with the Xano plugin, I see we can attach the elements straight to the API collection results.

For basic reading from the database (not upading or adding) Is it best practise to tie the elements directly to each desired xano result? Or is it preferable to loosely couple the results of each collection and use a workflow to populate variables? We could then link the elements to the variables to maintain the same level of separation and allow for minor field name changes on the xano backend without affecting the frontend code as much?
Or just connect directly as I see in the tutorials?

I look forward to your thoughts

[Joyce]

@kdjamo

I see we can attach the elements straight to the API collection results.

Hi @kdjamo

I’m not sure what you mean by this. Are you referring to Xano’s add-ons?

Also, what do you mean by “loosely couple the results of each collection and use a workflow to populate variables”?

Could you provide us with more information about what data you have in Xano and what data you want to display in WeWeb?