Fixes for dry run
Closes#261, #260, #129
By using dirty check, we choose to execute the api with an id or the whole action object. This also checks for new dynamic bindings and values. Also separated out the loading of widget and api pane.
See merge request theappsmith/internal-tools-client!156
Widget loading state.
Implements #297
Widgets have Dynamic properties can be bound to actions. ex: tableData: {{Users}}
Now when a bound action goes into running state, we put the corresponding widget also in a loading state.
See merge request theappsmith/internal-tools-client!152
Revamp widget property validation
Closes#290, #280
Moved to a architecture where a widget defines its validation and we pass safe values to the widget always. Property pane gets the store value and field level validation info
See merge request theappsmith/internal-tools-client!150
Creating docker images from the release and master branches
We now create docker images from the release and master branches and publish this to Docker hub. This is done to ensure that we can setup separate environments for production and staging. Required for stability and testing. This has been done by creating a Docker image by invoking the Dockerfile via the .gitlab-ci.yml file. The master branch will push to the release tag while the release branch will push to the release tag.
See merge request theappsmith/internal-tools-server!77
Selected row data is now updated on tableData change
Closes#277
Selected row data is now updated on tableData change
See merge request theappsmith/internal-tools-client!143
Property validations
Added validation for static and dynamic property changes of the widgets. A small validation error will be shown when the input or evaluated input is not matching the required type of the property input
See merge request theappsmith/internal-tools-client!124
Action can be unset. Actions are validated before executing.
Fixes#265#264
Previously, if you select an action in the property pane, there was not way to clear it. The actions can be removed now by clicking on a close button next to the dropdown.
Also, front-end code would try to execute an action even if there no actionId selected in the property pane. Now, there is a validation before action execution to check that.
See merge request theappsmith/internal-tools-client!140
Endpoint to view published page using just PageId
Fixes#83
We now return all the published layouts for a given pageId in the view mode. In the future, we will whittle the layouts down based on query parameters and other factors to return a single layout in the published page. Today, since most pages only have a single layout, there is no performance impact.
See merge request theappsmith/internal-tools-server!76
