I wouldn’t say sneaky, but I don’t check my email that much, and would like to see this information published to the main channel of announcements, or different channel.
Whereas I have a different account for each of my clients, can’t remember which ones I’ve requested the emails be disabled and get “ahem” copies of the newsletters!
In the past, when a databinding expression failed, it used to be just that: a failure. Anvil wouldn’t tell you what failed or why. I sometimes didn’t even use databinding because it was difficult to debug.
Now there are nice diagnostics telling you which databinding of which control failed.
And you can even click on it and the form appears.
And the control is selected.
And the focus is on the databinding.
I cloned the app, added a folder with some tests that I run on my computer using the uplink to interact with the database and other services, pushed and… it’s there!
The new editor has a much more refined way to work with branches in the git repository than the old editor.
Here is an use case that was not the reason why it has been designed as it was, but you can do it and it just saved me some time and helped me not playing with fire. Hence I think it qualifies as a sneaky new feature.
I was working on the dev branch, modifying many forms and modules and didn’t want to merge to prod because I would have very likely broken the production app.
I also did a little and safe change to an http endpoint. The new endpoint was compatible with the production app, but was in dev, so I couldn’t test it because it was called by another application that I didn’t want to modify.
So I copied the http endpoint code, set the current branch to prod, pasted the code, set the current branch back to dev, and now I had the new http endpoint working in the old production app, without needing any merge or modifying the 3rd application that was calling the http endpoint or doing anything crazy like I used to do.
I am not sure when this changed but I now see that errors in data bindings have a link in the output panel that takes you to the component with the error. I am sure it never used to be like this but definitely a nice little feature
When an event binding is registered to a component but the function doesn’t exist, there is now a nice output in the serial monitor telling you what failed. Has helped tremendously with some overdue code cleanup
Not sure if anyone has seen this - the Beta IDE checks the app and the database schema to see if there are any mismatches! It even helps you rectify what is not correct!! Nice additional Anvil Team