* Cypress tests to test if widgets are draggable
1. Added tests for all widgets to test if user is able to drag and drop them to canvas.
2. Re-organised Integration test folder according to the Pages.
* Updated package-lock.json file
Updated NPM to 7.20.0 and created this file again.
* Last update- package-lock.json
31 Sep-
Steps followed:
$ rm -rf node_modules/
$ npm cache clean --force
(Revert the changes in your package-lock.json file)
step 3 -> copy and paste the file from develop branch
$ npm i
still generating 21552 lines.
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
* widgets can be disabled
* removed whitespace
* move to styles definitions
* default values fixed with nullish operator
* proper data attributes
* generic resolver function for widget value
* renamed the style property
* design: change widget sidebar design
t # with '#' will be ignored, and an empty message aborts the commit.
* add empty text if search invalid
* fix: the expand query button getting cut
* make css changes
* small rgb fix
* add bg color
* feat: add integration section
* update categories
* add text, datepicker to common list
* remove space from title
* fix canvas alignment
Co-authored-by: navaneeth <navaneethpk@outlook.com>
