Should a fix be expected in Beta 24?
Fix was already in beta 23
The post was not marked, so wasn't sure.
What is the change you guys have finalized on? Will there be a recid for all queries or not?
And will the existing recid values be removed when I edit the query?
Additionally, same questions for for the collapsed value in JSON.
What should I expect?
@George Awaiting reply on what fix was applied here?
When you edit the query, at least open the query builder and then click OK, will remove the recid values. I hope it will not reappear again.
The collapsed value is stored in the json since it was requested by some users to save the state of the editor so that when you reopen the file it has the same state as when it was saved.
1 Like
Can we make this an option in the Wappler settings? It ultimately causes the same issue and I personally don’t care about saving that state if it resolves the main issue here
1 Like
Yes we can add an option for that
2 Likes
Wappler is fundamentally wrong when it comes to storing configuration like that. Any user preferences should be stored in a separate JSON so it can be excluded in .gitignore if necessary (e.g. when working in a team)
%s.userpref.json
4 Likes
+1 to this
@patrick Was finally able to test the changes here in the last couple of days.
The problem still persists.
- When I open and save a SA, Wappler sometimes removes all recids - which is what was expected - but not always.
- When I open every single query step save the SA, Wappler removes the recids.
- But, if I open the SA again, and work on some other step and save - the recids are back in random queries.
Can you please check the fix again?
I haven't seen RECID recently, but the collapsed ones continue to be a major annoyance and has the same effect as RECID. My server connects are long and I often have to collapse and uncollapse items. I end up with the below. The only actual changes is the long green at the bottom. The rest is all collapsed: false/true. It makes reviewing changes so tiresome.
