Server Actions naming display differences (minor)

Wappler Version : 3.5.1
Operating System : mac

Expected behavior

When selecting Server Actions, it should now be named API to match the change to Globals

Actual behavior

I’m suggesting Server Actions be renamed to API’s to prevent confusion. This for example is the panel that opens when creating a server route:

Screen Shot 2020-11-10 at 4.42.36 PM

2 Likes

It already is I believe.

That’sa different screen from my post. I’m asking that other panels match the one you posted. :slightly_smiling_face:

We should call them Server API Actions maybe on all dialogs.

Or just Server APIs ?

Whatever you think… just needs to be consistent. I notice it whole I make videos—I try to use the proper vernacular but this one tripped me up.

I actually think the use of Globals in two places is also going to be a point of confusion. There are globals that can be used on all server actions and globals within a single action.

yes definitely agree we should be 100% on the same vernacular.

The globals within a single Server Action are wrong indeed - those should be called “Input” (just as in App Connect Flows)

As for the naming of the SC Action picker - I think this will be the best:

image

Let me know if you find any other discrepancies.

4 Likes

Improved in Wappler 3.5.2

This topic was automatically closed after 2 days. New replies are no longer allowed.