Feedback on data fetching

[prakhargupta1]

General feedback: (Designer input needed)

• [x] After choosing a type of connection, I get stuck as to where should I head next? We should show a button that says Add new API and then take the user to API page with the connection already chosen.
• [x] On the left panel, we should highlight(always) the section user is currently on
• [x] We should keep MUI Toolpad header bar at all times, whether the App is in edit mode or deployed. If seeing a deployed App then it should also show 'Edit App' button
• [x] Show App name on the header
• [x] When a component is either on the extreme right or extreme left, only half red box comes over the canvas

When creating an API:

• [x] Put Update button on right and bold
• [x] When I update binding, there should not be a need to press the update button or keep it disabled if no change has been done
• [x] Every time I do anything on API page, there is a loader animation that keeps coming.
• [x] Until I press + button after entering API param_name and param_value, the inputs don't get saved

Doesn't happen in Appsmith/Retool:

• [x] Can I directly add a component value as the API parameter without using 'queryState'? Can we remove queryState entirely and manage scope from the APIs section only.
• [x] Why do I have to write query.prop to define a variable in API? In Retool only {{prop}} works

[Janpot]

We should keep MUI Toolpad header bar at all times, whether the App is in edit mode or deployed. If seeing a deployed App then it should also show 'Edit App' button

Let's decide on this next team meeting

Why do I have to write query.prop to define a variable in API? In Retool only {{prop}} works

It's a question of namespacing. It's a choice really, the more you make things top-level, the more they will clash with other names in the global scope.