Wappler Version : 6.6.0
Operating System : MacOS
What do you think should happen?
When editing an expression it should update the expression.
What actually happens?
Changes made to the expression are not implemented. Doesn't matter if it is a dataview filter or a dynamic attribute. Neither are editable.
Yes, reported here, bump
Thanks for the link. I wasn't sure when this started happening.
What is exactly the problem? When in code view the expression doesn’t change?
Code view is ment for editing code manually.
Is it all fine when you are just in design view of the expression builder?
Correct the code does not change at all. Doesn't matter if you are in code or design view. Edited using the interface not directly in the code.
If you make an error/mistake in setting your expression, you have to delete it and start over again.
Brad as explained here you have to go to design view to do automatic editing, code view is for editing in code.
@George Maybe the issue we have, is not well explained..
Basically, if you are placed ON the code editor, the visual expression builder is useless.
We are not talking about editing visually with the code editor.
Example:
If you are on design view and do this:
The output on design view is:
And on the code view is:
NOW if you are on the code view and do this:
The output on the code view is STILL:
And that is a really mess, doesn't have sense that code is not changed.
Because on design view the code is created correctly (if you go from design to code).
Are you sure this is an expected behaviour?
The question here, is:
Why the design tab, can translate the visual into code (you can change from design to code and see it perfectly as I said above) but if you're on code view, you can not see the correct result?
I was only in code view to show that the code doesn’t change. Even in design view you can’t edit expressions.
For example something as simple as if you set an expression to of value is empty and hit save . Realize that you made a mistake and go back in and change it to is not empty and hit save. The change is not saved.
You have to completely remove the expression and start over.
So you can't edit any expression at all?
There must be something very fundamentally wrong there.
Please make a short video and send also a debug log as well.
I think you and Brad are talking about very different things.
Do you have a situation that doesn't reflect your changes in design view?
No, but I can't understand why the code on code view is not changed when you edit visually:
So:
We can edit visually on design view and then change to code view and see the correct output
But we can't edit visually on code view.
If this is an expected behavior, what's the point of having a code view?
If we need to change something and we edit visually using the Visual Expression builder, BUT we are on the code view, then changes are not applied and that can create a big confussion.
So it has no sense.
Instead of editing using the interface, then you should remove the code view and edit outside using the code view of the main editor (and not the popup)
Sorry, I can't understand just simple why:
Edit visually on design and go to code: Ok
Edit visually on code: Wrong
yes I get your point and that is a different discussion, but in this topic it creates only confusion because Brad is telling that he can't edit expressions at all... also in design view
I see what is happening that is causing some confusion. I did some further testing.
1: Create a simple expression (the expression shows correctly in the design view) and click on Save. The proper code is inserted in the page.
2: Go to edit the expression using the UI. The changes are not reflected in the design view panel. I would expect it would change to reflect the changes made in the expression. So this made me think the expression wasn't getting updated.
3: However, when you do click on save, the proper updated expression gets reflected on the page.
So in reality it is working, just design view does not update in real time to reflect the updates.
Yes, this is a little tricky, but @brad can you click outside after the edit and see the change?
See the video till the end, when I wait some few seconds and then click some other place:
Does it work like that?
Sorry @George it was not my intention and I was taking advantage of using an unlisted topic to not create confussion with the rest of the users.
I just saw the first video that brad uploaded and thought that we are talking about the same.
Please forgive my lack of english here 
Ah, yes, I just tested and it does update if I click elsewhere in the UI.
But yes naturally when you haven’t left the input field yet the expression is not updated… we are not updating on each keystroke, only when you tab or click outside the input field, the expression is updated.
So that is your whole trouble?
It was just confusing for me. Now that I know how it works I am fine. It's all good.
