The context is provided here.
The Mendix Pluggable Widget API is well-typed and effective for developing robust widgets. However, during my development process, I noticed that there are cases where it’s necessary to store user-specific configurations on the server. For example, the attribute used to store user configurations in Data Grid 2 illustrates this need well. In addition, based on our customer feedback, many users would appreciate having personalized configurations available.
In the widget I’m currently developing, I also need to save some configuration data in the database. For the sake of simplicity, developer convenience, and improved development speed, we want to avoid requiring app developers to pass values to a nanoflow for storage—especially since they won’t be able to manipulate the configuration data directly.
According to my [question](https://community.mendix.com/link/space/widgets/questions/142316) posted on the Mendix Community, the final solution is to use `mx.data.commit` to explicitly commit the local data to the attribute. However, mentioned, this approach is considered an anti-pattern for widget development and does not align with TypeScript standards. Is it possible to incorporate such data manipulate action into the Pluggable Widget APIs so that it can be maintained upstream?