* Added no codition section when aggregates are not available
* Added feature to add aggregate condition and display it accordingly
* Added feature to change the aggregateFx option
* Added feature to update column option in the aggregate
* Added feature to delete the aggregate
* Disabling the group by according to valid condition but without tooltip
* Added flow for deleting aggregate
* feat: migration and configuration changes to support aggregation in tooljet database
* added functionality for join table operations
* Dropdown styles
* Showing section for aggregate dropdown for joinTable operation
* Added gap in multiple aggregate conditions
* Added table_id in aggregate condition
* Added custom placeholder
Adjusted width of add condition of aggregate
* Refactored logic for disable group_by field
Added tooltip when group by is disabled
* Updated aggregateFx to aggFx and groupBy to group_by
* feat: group_by and aggregate option in list rows
* added table name for aggregate dropdown value in joinTable operation
* Get the group by options
* value of aggregate column dropdown in join table operation
* Added error and success message for aggregate deletion
* Spacing adjustments
* Clear the unwanted code
* Updated the stucture of aggregate
* Updated the structure of group_by
* Fix: Query builder breaking due to undefined values
* feat: logic used to aggregate on joins
* Removing async
* fix: app is crashing
* feat: statement timeout at database level and user session level configuration can be done for ToolJet database
* Added min and max width to dropdown in tooljetdb query manager
* Added description
* Adding width as 80 percentage when description is not avaialable
* New Postgrest change for render related to Aggregate (#10175)
* New Postgrest change for render related to Aggregate and group by functionality
* correction in PGRST_DB_ENABLE_AGGREGATE value
* Adding the env variable PGRST_DB_PRE_CONFIG
* Adding the new postgrest related env changes to CE specific files
* fix: updated env variable naming for aggregates
* Showing description at the bottom for aggregate fx
* Fixing typo error
* Showing tick mark on selected item in dropdown when isMulti is false
* Updated requested changes
* Showing some description when option is not focused or selected
* Updated the component name to AggregateFilter
* fix: updated env variable to enable aggregation in tooljet database
* refactor: new wrapper to create migration connection for tooljet database
* fix: custom error message for aggregation errors has been handled for list_rows operation
* fix: code review fixes
* fix: aggregate function validation typo is updated
* fix: empty validation for Select and Aggregate fields
* postgrest changes for cypress
* removed PGRST_DB_ENABLE_AGGREGATE
---------
Co-authored-by: Ganesh Kumar <ganesh8056234@gmail.com>
Co-authored-by: Adish M <44204658+adishM98@users.noreply.github.com>
Co-authored-by: Adish M <adish.madhu@gmail.com>
* add plugins to docker compose
* build common
* change cmd
* build:pkgs
* fix'
* temp: add named vol
* update docker-compose for plugins dev
* update seed script to transpile only
* fix ci
* fix ci
Co-authored-by: gandharv <gandharvkumargarg@gmail.com>
* Add functionality to decide whether front-end should be served from server
This commit makes the server allow flag `--serve-frontend`, providing
which, will make the server serve the front-end at route '/'. Otherwise
it won't serve the front-end.
* Use env variable to enable serving client from a server end-point
* Add documentation for SERVE_CLIENT env var
* update docker-compose and docs for docker dev setup
* specify test environment explicitly on npm scripts
* fix migrations to be picked up from either root or dist folder
* fix default slug update
* separate dockerfile for tooljet client in development mode
* production dockerfile for tooljet client
* reference the tooljet clients dev dockerfile in the docker-compose file
* use a fallback url for API_URL in cases where TOOLJET_SERVER_URL is not defined
* nginx config file for the front-end
* docker-compose file for production deploys
* dont run postgres inside docker-compose
* use an entrypoint script for setting the server host for nginx
* separate volume for fallback certs
* add docs for docker-compose deployment
* add required database keys in the .env.example file
* address review comments
* new dockerfile for development
* reference the development dockerfile in docker-compose
* remove explicit RAILS_ENV=production in development dockerfile
