Merge "dynamic content" and "expressions"

[thinkOfaNumber]

I've been developing logic apps for production systems for about 2 years now. I find there's no real difference between "dynamic content" and "expressions". Both can be used to get outputs from previous actions by searching. Both can create the exact same json output. The only functional differences are:

1. "dynamic content" doesn't allow expressions, but expressions do allow "dynamic content".
2. "dynamic content" can't be edited

In my opinion, 2. is a real pain. Often I will enter an expression (which is just something like body('action_name') and it gets converted to dynamic content, so I can't come back and edit it later. This is a problem because some dynamic content can be complex, such as body('action_name')?['property']?[0]?['another_property']. I may realise I need to change another_property to another_property2, but I can't because it's not editable. I have to recreate the whole path again. It's not possible to use the search feature to do this for two reasons:

1. if there is no "parse" or schema available to the editor, it doesn't know what the outputs are and you have to build the expression up yourself
2. If you select a known schema with an array, the editor will automatically add your action into a foreach loop, when that's not always what you want.

So in my opinion they're basically the same thing, but you're hampered because the editor decides that you can't edit one type of expression. It would be much easier if they both just became "expressions", which already includes dynamic content, and is always editable.