[Bug] WeWeb branching feature with Xano

[Jack]

Hi there,

I have my weweb editor environment hooked up to my ‘develop’ xano branch, but when working in the editor, an endpoint needs to be in the live branch to show up in a dropdown to select it.

Example (screenshots below):

1. Add endpoint in ‘develop’ branch
2. Try to add as a collection. nothing shows up (remember that weweb editor is connected to ‘develop’ branch in xano plugin and xano auth plugin)
3. Merge the ‘develop’ branch to the ‘live’ xano branch
4. Refresh in weweb and it shows up

It defeats the purpose of branching if I need to merge all new endpoints into the ‘live’ branch to even configure them in WeWeb. The idea is that my editor would fully use my ‘develop’ branch, but it seems like it is reading the endpoints in the live version and then just using the logic within the develop branch? Not sure but I’m surprised the branching feature shipped with such a major bug.

Has anyone else ran into this? Easy way to fix?

Jack

Not showing up:

Only showing up after ‘develop’ is merged to ‘live’

[Alexis]

Hi, its a current limitation we have, an improvement is in QA and should be released in the next two weeks.

For now, even if you put another branch we can only parse the specification from the live branch, so in the editor you’re still seeing the live endpoints and input, but if you execute them it will hit the branch you select.
So your branch has to share the same endpoints and inputs as the live branch if you want to use it (but it can have a different process inside the endpoint). Of course its a huge constraint and we will take care to remove it in a next release.

[Jack]

Sounds good. Thanks for the clarification @Alexis. Looking forward to the fix!