When webpack bundles your source code, it can become difficult to track down errors and warnings to their original location. For example, if you bundle three source files (a.js, b.js, and c.js) into one bundle (bundle.js) and one of the source files contains an error, the stack trace will point to bundle.js. This isn't always helpful as you probably want to know exactly which source file the error came from.
In order to make it easier to track down errors and warnings, JavaScript offers source maps, which map your compiled code back to your original source code. If an error originates from b.js, the source map will tell you exactly that.
more info: https://webpack.js.org/guides/development/#using-source-maps
* feat: add rest api new design
* fix page break on create/save query
* remove console.log
* align the i/p fields
* rename files
* remove border from i/p
* remove hover styles
* fix: filter empty headers, url_params, body
* fix when editmode headers empty
* fix the options on preview getting null
* fix navlink color on dark mode
* add color for non active tab in dark mode
* feat: add star rating widget
* add events, properties
* add the number of stars as variable
* fix animation
* add half star logic, properties, definations
* add hover index property
* on dismiss show star outline
* show tooltip on hover + fix half icon display on click
* make text inline
* feat: add import svg as react component
* update star rating component for managing color change
* fix: conflicts
* Delete half-star.svg
* Delete star.svg
* change default color to gold
* fix widget settings events
* add default selection of stars
* change default selection to 5
* css changes
* add star rating onchange fix
* 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
