This is not a bug??
I used the constructor to build a sentence and when editing, he change for error and put ==1
This is a great opportunity for DIY. As you become more proficient, Wappler's bugs become far less relevant. It's a learning exercise.
I completely agree, but the code created, whether by the builder or manually, should never be changed by the editor, to an error state. This makes our work even harder and we need the tool to gain productivity and not harm it!
I found exactly the problem!
when the expression ends with .default(n) the editor removes default(n) and adds ==1, causing the bug, but if I put for example: .default(1)==1 the editor respects it and does not remove .default(1)==1, but if I put only .default(1), it causes the whole problem!
So you completely agree and don't agree?
I agree that we gain knowledge when we eventually execute manual code (DIY), but the editor shouldn't ruin what we do!
and I also believe that identified and fixed bugs help new users to avoid the same problems and further improve the Wappler platform!
Now the true test is, does this make it into the Wappler team's list of bugs to fix or does it remain unfixed because only you have run across it (or at the least reported it)? That's another can of worms I just teased open.
Bump!
Yes, i have seen "==1" added recenty also when editing conditions and from memory, not just when using the expression builder. I assumed it was caused by me messing with the code manually but looks like it may not be.
Will try and get a log
1 Like