I’ve noticed that some features that are useful for newbies to get started (and incredibly unsafe), are also available for professionals to trip on (such as having forms being able to directly read and write data tables)
I don’t like promoting unsafe newbie practices. It trains people incorrectly, but it’s unlikely that Anvil is going to agree with me on this.
Also, each app generally has a list of common dependencies, that I don’t want to add over and over again for each new app, so I’m proposing the following template / app configuration functionality for existing and new apps:
Playground:
Run around and do all the unsafe stuff you like. Let the forms access the data tables and have as many security holes as you like, and other such things
Professional:
Checkbox Option: Data tables don’t even have the option to be accessed directly by forms or mix and match where only reads are available.
Also, A new server role / user validation service is added, inspired from Authorisation — Anvil Extras documentation and other such strict enforcements.
Custom:
Create from existing or completely new template. Import and enable whatever you like. Custom components, services, data tables, etc…