Refactoring

[Harm_Kindt]

Hello everyone,

I'm a new user of Wappler, and I'm really enjoying it, especially all the new features on the horizon.

This might be a bit of a long shot, but coming from a development background where I used PhpStorm as an editor, I loved the refactoring functionality. For instance, when changing an object or variable, PhpStorm provided an overview of where these items were used, allowing for easy refactoring.

Refactoring in Wappler would be fantastic! But at the very least, having a list of locations impacted by a change would be incredibly helpful.

Best regards,

Harm.

[jellederijke]

Sounds like an amazing feature, @Harm_Kindt! Take my vote

[R4v3n]

I like this idea a lot!

[Apple]

Hi, welcome

Related:

A way to keep all wappler elements in sync if one of them is modified. Refactoring QoL

One thing that Bubble gets right is using internal non-modifiable ids for every single element in their platform for each app. This could be a data type(DB table), data item(row), UI element, etc The purpose of this is to be able to abstract what you visualize from how it all connects behind. I can change that name of a field in one place and I won’t have to change it elsewhere because bubble internally is establishing a link between them via internal non mutable IDs. It would help a lot if W…

[Harm_Kindt]

Thanks, yes this is what makes life much easier.

[karh]

This + the recent additions you guys are making are really making Wappler great and feels like an amazing powertool again, opposed to feeling like it saves time in certain area's and costs time in others.