This is to ensure that setting the createdAt nad updatedAt properties by spring-data will still succeed even if the client doesn't provide us with the datasource details.
Adding the field shouldCacheResponse to the ActionExecutionResult to make the response caching generic across various plugins
Now the plugin executor will decide if the action should cache the response based on their own result sets. This ensures that we are not tied to the status code that is primarily an HTTP construct.
This MR also contains changes for the CurlParserService that should have been merged in !204 but didn't because of a bad merge with !200. The test case for CurlParserService has been commented out for now.
See merge request theappsmith/internal-tools-server!207
Creating an embedded datasource for the action
Now the user can create an embedded datasource as well as a saved datasource for the action.
This MR also fixes the import for a curl command by setting defaults when an action is created via the curl command. For now, the curl command only accepts short flags and not the long form flags.
See merge request theappsmith/internal-tools-server!204
When deleting a page, also remove it from the application page cache.
This fixes the bug where the application could not be published because it assumed a page existed when that page had been deleted.
See merge request theappsmith/internal-tools-server!205
Added valueOptions to store the permitted values for a key (which is being sent by rapidApi today)
See merge request theappsmith/internal-tools-server!202
We now create another list from the value provided in the properties file. All checks in the codebase are performed against this list. This ensures that there are no NPE and exceptions when the property oauth2.allowed-domains is removed from the properties file.
Correcting the error response returned by the AclFilter to match the ErrorDTO...
Correcting the error response returned by the AclFilter to match the ErrorDTO returned from controller functions
This ensures consistent responses from different parts of our application. The client can then rely on the server to provide a constistent response structure.
See merge request theappsmith/internal-tools-server!194
This ensures consistent responses from different parts of our application. The client can then rely on the server to provide a constistent response structure.
Renaming isPaginated to PaginationType to support different types of pagination on the frontend
If the API is paginated via the table's page number, then the next and prev URLs in the action don't play any role. Those fields are only required when the paginationType is of type URL. In all other scenarios, the action is executed normally.
See merge request theappsmith/internal-tools-server!192
If the API is paginated via the table's page number, then the next and prev URLs in the action don't play any role. Those fields are only required when the paginationType is of type URL. In all other scenarios, the action is executed normally.
Now, regardless of the route with which an organization is created (invitation, signup or self-create by user), the correct groups and permissions are assigned to the user.
Adding functionality to archive page in an application
The code for archiving an application has been moved to ApplicationPageService so that both the PageService and ApplicationService can access it. This ensures that we follow the same code path when archiving an application and when archiving pages.
See merge request theappsmith/internal-tools-server!190
Adding default implementation in BaseRepositoryImpl for default JPA queries defined by Spring Data.
See merge request theappsmith/internal-tools-server!189
We override the SimpleReactiveMongoRepository with our custom implementation to add criteria for filtering soft deleted records.
Also, adding a new function to archive record instead of a hard delete.
