2019-12-16 08:49:10 +00:00
|
|
|
@import "~normalize.css";
|
|
|
|
|
@import "~@blueprintjs/core/lib/css/blueprint.css";
|
|
|
|
|
@import "~@blueprintjs/icons/lib/css/blueprint-icons.css";
|
2021-12-24 07:25:25 +00:00
|
|
|
@import "theme/colors.css";
|
|
|
|
|
@import "theme/defaultTheme.css";
|
2022-08-05 04:46:42 +00:00
|
|
|
@import "theme/wds.css";
|
2023-04-13 13:18:37 +00:00
|
|
|
@import "assets/fonts/custom/index.css";
|
2019-12-16 08:49:10 +00:00
|
|
|
|
2023-05-19 18:37:06 +00:00
|
|
|
:root {
|
2023-06-20 09:04:13 +00:00
|
|
|
/* TODO: This needs to be fixed! This override is to maintain branding changes. */
|
2023-05-19 18:37:06 +00:00
|
|
|
--ads-color-background-secondary: var(--ads-v2-color-bg-subtle);
|
|
|
|
|
}
|
|
|
|
|
|
2019-01-21 15:11:10 +00:00
|
|
|
body {
|
|
|
|
|
margin: 0;
|
|
|
|
|
padding: 0;
|
chore: upgrade to prettier v2 + enforce import types (#21013)Co-authored-by: Satish Gandham <hello@satishgandham.com> Co-authored-by: Satish Gandham <satish.iitg@gmail.com>
## Description
This PR upgrades Prettier to v2 + enforces TypeScript’s [`import
type`](https://www.typescriptlang.org/docs/handbook/release-notes/typescript-3-8.html#type-only-imports-and-export)
syntax where applicable. It’s submitted as a separate PR so we can merge
it easily.
As a part of this PR, we reformat the codebase heavily:
- add `import type` everywhere where it’s required, and
- re-format the code to account for Prettier 2’s breaking changes:
https://prettier.io/blog/2020/03/21/2.0.0.html#breaking-changes
This PR is submitted against `release` to make sure all new code by team
members will adhere to new formatting standards, and we’ll have fewer
conflicts when merging `bundle-optimizations` into `release`. (I’ll
merge `release` back into `bundle-optimizations` once this PR is
merged.)
### Why is this needed?
This PR is needed because, for the Lodash optimization from
https://github.com/appsmithorg/appsmith/commit/7cbb12af886621256224be0c93e6a465dd710ad3,
we need to use `import type`. Otherwise, `babel-plugin-lodash` complains
that `LoDashStatic` is not a lodash function.
However, just using `import type` in the current codebase will give you
this:
<img width="962" alt="Screenshot 2023-03-08 at 17 45 59"
src="https://user-images.githubusercontent.com/2953267/223775744-407afa0c-e8b9-44a1-90f9-b879348da57f.png">
That’s because Prettier 1 can’t parse `import type` at all. To parse it,
we need to upgrade to Prettier 2.
### Why enforce `import type`?
Apart from just enabling `import type` support, this PR enforces
specifying `import type` everywhere it’s needed. (Developers will get
immediate TypeScript and ESLint errors when they forget to do so.)
I’m doing this because I believe `import type` improves DX and makes
refactorings easier.
Let’s say you had a few imports like below. Can you tell which of these
imports will increase the bundle size? (Tip: it’s not all of them!)
```ts
// app/client/src/workers/Linting/utils.ts
import { Position } from "codemirror";
import { LintError as JSHintError, LintOptions } from "jshint";
import { get, isEmpty, isNumber, keys, last, set } from "lodash";
```
It’s pretty hard, right?
What about now?
```ts
// app/client/src/workers/Linting/utils.ts
import type { Position } from "codemirror";
import type { LintError as JSHintError, LintOptions } from "jshint";
import { get, isEmpty, isNumber, keys, last, set } from "lodash";
```
Now, it’s clear that only `lodash` will be bundled.
This helps developers to see which imports are problematic, but it
_also_ helps with refactorings. Now, if you want to see where
`codemirror` is bundled, you can just grep for `import \{.*\} from
"codemirror"` – and you won’t get any type-only imports.
This also helps (some) bundlers. Upon transpiling, TypeScript erases
type-only imports completely. In some environment (not ours), this makes
the bundle smaller, as the bundler doesn’t need to bundle type-only
imports anymore.
## Type of change
- Chore (housekeeping or task changes that don't impact user perception)
## How Has This Been Tested?
This was tested to not break the build.
### Test Plan
> Add Testsmith test cases links that relate to this PR
### Issues raised during DP testing
> Link issues raised during DP testing for better visiblity and tracking
(copy link from comments dropped on this PR)
## Checklist:
### Dev activity
- [x] My code follows the style guidelines of this project
- [ ] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [x] My changes generate no new warnings
- [ ] I have added tests that prove my fix is effective or that my
feature works
- [ ] New and existing unit tests pass locally with my changes
- [ ] PR is being merged under a feature flag
### QA activity:
- [ ] Test plan has been approved by relevant developers
- [ ] Test plan has been peer reviewed by QA
- [ ] Cypress test cases have been added and approved by either SDET or
manual QA
- [ ] Organized project review call with relevant stakeholders after
Round 1/2 of QA
- [ ] Added Test Plan Approved label after reveiwing all Cypress test
---------
Co-authored-by: Satish Gandham <hello@satishgandham.com>
Co-authored-by: Satish Gandham <satish.iitg@gmail.com>
2023-03-16 11:41:47 +00:00
|
|
|
background-color: #fff !important;
|
2023-05-19 18:37:06 +00:00
|
|
|
color: var(--ads-v2-color-fg);
|
2019-01-21 15:11:10 +00:00
|
|
|
}
|
|
|
|
|
|
2022-03-10 05:38:50 +00:00
|
|
|
body.dragging * {
|
2020-08-14 07:18:30 +00:00
|
|
|
cursor: grabbing !important;
|
|
|
|
|
}
|
|
|
|
|
|
2023-05-19 18:37:06 +00:00
|
|
|
/**
|
|
|
|
|
Disable outline completely from all components
|
|
|
|
|
*/
|
|
|
|
|
:focus,
|
|
|
|
|
:focus-visible {
|
|
|
|
|
outline: none !important;
|
|
|
|
|
outline-offset: 0 !important;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
Disable outline for adsv2 select component
|
|
|
|
|
*/
|
|
|
|
|
.ads-v2-select.rc-select-focused {
|
|
|
|
|
outline: none !important;
|
|
|
|
|
outline-offset: 0 !important;
|
|
|
|
|
}
|
|
|
|
|
|
2023-06-08 09:28:29 +00:00
|
|
|
#root.overlay {
|
2023-04-14 07:19:42 +00:00
|
|
|
opacity: 0;
|
|
|
|
|
pointer-events: none;
|
|
|
|
|
}
|
|
|
|
|
|
2019-01-21 15:11:10 +00:00
|
|
|
code {
|
|
|
|
|
font-family: source-code-pro, Menlo, Monaco, Consolas, "Courier New",
|
chore: upgrade to prettier v2 + enforce import types (#21013)Co-authored-by: Satish Gandham <hello@satishgandham.com> Co-authored-by: Satish Gandham <satish.iitg@gmail.com>
## Description
This PR upgrades Prettier to v2 + enforces TypeScript’s [`import
type`](https://www.typescriptlang.org/docs/handbook/release-notes/typescript-3-8.html#type-only-imports-and-export)
syntax where applicable. It’s submitted as a separate PR so we can merge
it easily.
As a part of this PR, we reformat the codebase heavily:
- add `import type` everywhere where it’s required, and
- re-format the code to account for Prettier 2’s breaking changes:
https://prettier.io/blog/2020/03/21/2.0.0.html#breaking-changes
This PR is submitted against `release` to make sure all new code by team
members will adhere to new formatting standards, and we’ll have fewer
conflicts when merging `bundle-optimizations` into `release`. (I’ll
merge `release` back into `bundle-optimizations` once this PR is
merged.)
### Why is this needed?
This PR is needed because, for the Lodash optimization from
https://github.com/appsmithorg/appsmith/commit/7cbb12af886621256224be0c93e6a465dd710ad3,
we need to use `import type`. Otherwise, `babel-plugin-lodash` complains
that `LoDashStatic` is not a lodash function.
However, just using `import type` in the current codebase will give you
this:
<img width="962" alt="Screenshot 2023-03-08 at 17 45 59"
src="https://user-images.githubusercontent.com/2953267/223775744-407afa0c-e8b9-44a1-90f9-b879348da57f.png">
That’s because Prettier 1 can’t parse `import type` at all. To parse it,
we need to upgrade to Prettier 2.
### Why enforce `import type`?
Apart from just enabling `import type` support, this PR enforces
specifying `import type` everywhere it’s needed. (Developers will get
immediate TypeScript and ESLint errors when they forget to do so.)
I’m doing this because I believe `import type` improves DX and makes
refactorings easier.
Let’s say you had a few imports like below. Can you tell which of these
imports will increase the bundle size? (Tip: it’s not all of them!)
```ts
// app/client/src/workers/Linting/utils.ts
import { Position } from "codemirror";
import { LintError as JSHintError, LintOptions } from "jshint";
import { get, isEmpty, isNumber, keys, last, set } from "lodash";
```
It’s pretty hard, right?
What about now?
```ts
// app/client/src/workers/Linting/utils.ts
import type { Position } from "codemirror";
import type { LintError as JSHintError, LintOptions } from "jshint";
import { get, isEmpty, isNumber, keys, last, set } from "lodash";
```
Now, it’s clear that only `lodash` will be bundled.
This helps developers to see which imports are problematic, but it
_also_ helps with refactorings. Now, if you want to see where
`codemirror` is bundled, you can just grep for `import \{.*\} from
"codemirror"` – and you won’t get any type-only imports.
This also helps (some) bundlers. Upon transpiling, TypeScript erases
type-only imports completely. In some environment (not ours), this makes
the bundle smaller, as the bundler doesn’t need to bundle type-only
imports anymore.
## Type of change
- Chore (housekeeping or task changes that don't impact user perception)
## How Has This Been Tested?
This was tested to not break the build.
### Test Plan
> Add Testsmith test cases links that relate to this PR
### Issues raised during DP testing
> Link issues raised during DP testing for better visiblity and tracking
(copy link from comments dropped on this PR)
## Checklist:
### Dev activity
- [x] My code follows the style guidelines of this project
- [ ] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [x] My changes generate no new warnings
- [ ] I have added tests that prove my fix is effective or that my
feature works
- [ ] New and existing unit tests pass locally with my changes
- [ ] PR is being merged under a feature flag
### QA activity:
- [ ] Test plan has been approved by relevant developers
- [ ] Test plan has been peer reviewed by QA
- [ ] Cypress test cases have been added and approved by either SDET or
manual QA
- [ ] Organized project review call with relevant stakeholders after
Round 1/2 of QA
- [ ] Added Test Plan Approved label after reveiwing all Cypress test
---------
Co-authored-by: Satish Gandham <hello@satishgandham.com>
Co-authored-by: Satish Gandham <satish.iitg@gmail.com>
2023-03-16 11:41:47 +00:00
|
|
|
monospace;
|
2019-01-21 15:11:10 +00:00
|
|
|
}
|
2019-11-21 10:52:49 +00:00
|
|
|
|
|
|
|
|
div.bp3-select-popover .bp3-popover-content {
|
|
|
|
|
padding: 0;
|
|
|
|
|
}
|
|
|
|
|
|
2019-12-23 12:16:33 +00:00
|
|
|
span.bp3-popover-target {
|
2021-11-23 08:01:46 +00:00
|
|
|
display: flex;
|
|
|
|
|
width: 100%;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
span.bp3-popover-target > * {
|
|
|
|
|
flex-grow: 1;
|
2023-04-11 08:10:15 +00:00
|
|
|
}
|
|
|
|
|
|
2023-05-19 18:37:06 +00:00
|
|
|
.bp3-popover,
|
|
|
|
|
.bp3-popover2 {
|
|
|
|
|
box-shadow: var(--ads-v2-shadow-popovers) !important;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
.bp3-popover2-content {
|
|
|
|
|
border-radius: var(--ads-v2-border-radius) !important;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
.action-selector-popup {
|
|
|
|
|
background-color: var(--ads-v2-color-bg);
|
|
|
|
|
border-radius: var(--ads-v2-border-radius) !important;
|
|
|
|
|
border: 1px solid var(--ads-v2-color-border-muted) !important;
|
|
|
|
|
}
|
|
|
|
|
|
2023-04-11 08:10:15 +00:00
|
|
|
.action-selector-popup span.bp3-popover-target > * {
|
2023-04-06 16:49:12 +00:00
|
|
|
max-width: 100%;
|
|
|
|
|
}
|
|
|
|
|
|
2023-05-19 18:37:06 +00:00
|
|
|
add-action.disabled span {
|
|
|
|
|
cursor: not-allowed;
|
|
|
|
|
}
|
|
|
|
|
|
2023-04-11 08:10:15 +00:00
|
|
|
.action-selector-popup .bp3-button-text {
|
2023-04-06 16:49:12 +00:00
|
|
|
text-overflow: ellipsis;
|
|
|
|
|
overflow: hidden;
|
|
|
|
|
min-width: 0;
|
2019-12-23 12:16:33 +00:00
|
|
|
}
|
|
|
|
|
|
2023-05-25 12:38:51 +00:00
|
|
|
/**
|
2023-05-19 18:37:06 +00:00
|
|
|
action selector block styles
|
|
|
|
|
**/
|
|
|
|
|
.bp3-submenu.bp3-popover > .bp3-popover-content {
|
|
|
|
|
box-shadow: none;
|
2019-12-03 09:21:06 +00:00
|
|
|
}
|
|
|
|
|
|
2023-05-19 18:37:06 +00:00
|
|
|
.action-card-border {
|
|
|
|
|
border-color: var(--ads-v2-color-border);
|
2020-01-15 04:49:36 +00:00
|
|
|
}
|
|
|
|
|
|
2023-05-19 18:37:06 +00:00
|
|
|
.action-card-next-selected {
|
|
|
|
|
border-bottom: 1px solid var(--ads-v2-color-border-emphasis-plus);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
.action-card-border-selected {
|
|
|
|
|
border-color: var(--ads-v2-color-border-emphasis-plus) !important;
|
2020-02-18 10:41:52 +00:00
|
|
|
}
|
|
|
|
|
|
2023-05-19 18:37:06 +00:00
|
|
|
.action-card-last-block {
|
|
|
|
|
border-radius: 0px 0px var(--ads-v2-border-radius) var(--ads-v2-border-radius);
|
2020-02-18 10:41:52 +00:00
|
|
|
}
|
2022-03-10 05:38:50 +00:00
|
|
|
|
2023-05-19 18:37:06 +00:00
|
|
|
.main-block-radius {
|
|
|
|
|
border-radius: var(--ads-v2-border-radius);
|
2020-02-18 10:41:52 +00:00
|
|
|
}
|
2020-09-16 10:28:01 +00:00
|
|
|
|
2023-05-19 18:37:06 +00:00
|
|
|
.main-block-radius-selected {
|
|
|
|
|
border-radius: var(--ads-v2-border-radius) var(--ads-v2-border-radius) 0px 0px;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
.bp3-popover.bp3-minimal.bp3-submenu {
|
|
|
|
|
padding-right: 0px;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
div.bp3-popover-arrow {
|
|
|
|
|
display: none;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
.bp3-button.bp3-loading {
|
|
|
|
|
cursor: default !important;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
.display-none {
|
|
|
|
|
display: none;
|
2020-09-16 10:28:01 +00:00
|
|
|
}
|
2020-12-30 09:06:24 +00:00
|
|
|
|
2021-07-15 10:56:18 +00:00
|
|
|
.t--editor-appname-menu-portal {
|
|
|
|
|
z-index: 9 !important;
|
|
|
|
|
}
|
|
|
|
|
|
2021-02-08 07:30:01 +00:00
|
|
|
.bp3-popover .bp3-input {
|
|
|
|
|
outline: 0;
|
|
|
|
|
box-shadow: none;
|
2023-05-19 18:37:06 +00:00
|
|
|
border: 1px solid var(--ads-v2-color-border);
|
|
|
|
|
border-radius: var(--ads-v2-border-radius) !important;
|
2021-02-08 07:30:01 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
.bp3-popover .bp3-input:focus {
|
2023-05-19 18:37:06 +00:00
|
|
|
border-color: var(--ads-v2-color-border-emphasis);
|
2021-02-08 07:30:01 +00:00
|
|
|
outline: 0;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
.bp3-popover.bp3-minimal {
|
|
|
|
|
margin-top: 8px !important;
|
|
|
|
|
}
|
|
|
|
|
|
2023-04-06 16:49:12 +00:00
|
|
|
.bp3-popover.bp3-minimal.action-selector-dropdown {
|
|
|
|
|
margin-top: 0px !important;
|
|
|
|
|
}
|
|
|
|
|
|
2022-03-10 05:38:50 +00:00
|
|
|
.layout-control.bp3-popover.bp3-minimal {
|
2021-03-29 15:47:22 +00:00
|
|
|
margin-top: 8px !important;
|
2021-03-03 05:26:47 +00:00
|
|
|
}
|
|
|
|
|
|
2021-10-26 05:17:59 +00:00
|
|
|
.bp3-popover.none-shadow-popover {
|
|
|
|
|
box-shadow: none;
|
|
|
|
|
border: 0px;
|
|
|
|
|
}
|
2021-03-03 05:26:47 +00:00
|
|
|
|
2021-02-08 07:30:01 +00:00
|
|
|
.bp3-datepicker {
|
|
|
|
|
border-radius: 0 !important;
|
|
|
|
|
}
|
|
|
|
|
|
2021-05-19 07:20:00 +00:00
|
|
|
/* making both the Modal layer and the Dropdown layer */
|
chore: upgrade to prettier v2 + enforce import types (#21013)Co-authored-by: Satish Gandham <hello@satishgandham.com> Co-authored-by: Satish Gandham <satish.iitg@gmail.com>
## Description
This PR upgrades Prettier to v2 + enforces TypeScript’s [`import
type`](https://www.typescriptlang.org/docs/handbook/release-notes/typescript-3-8.html#type-only-imports-and-export)
syntax where applicable. It’s submitted as a separate PR so we can merge
it easily.
As a part of this PR, we reformat the codebase heavily:
- add `import type` everywhere where it’s required, and
- re-format the code to account for Prettier 2’s breaking changes:
https://prettier.io/blog/2020/03/21/2.0.0.html#breaking-changes
This PR is submitted against `release` to make sure all new code by team
members will adhere to new formatting standards, and we’ll have fewer
conflicts when merging `bundle-optimizations` into `release`. (I’ll
merge `release` back into `bundle-optimizations` once this PR is
merged.)
### Why is this needed?
This PR is needed because, for the Lodash optimization from
https://github.com/appsmithorg/appsmith/commit/7cbb12af886621256224be0c93e6a465dd710ad3,
we need to use `import type`. Otherwise, `babel-plugin-lodash` complains
that `LoDashStatic` is not a lodash function.
However, just using `import type` in the current codebase will give you
this:
<img width="962" alt="Screenshot 2023-03-08 at 17 45 59"
src="https://user-images.githubusercontent.com/2953267/223775744-407afa0c-e8b9-44a1-90f9-b879348da57f.png">
That’s because Prettier 1 can’t parse `import type` at all. To parse it,
we need to upgrade to Prettier 2.
### Why enforce `import type`?
Apart from just enabling `import type` support, this PR enforces
specifying `import type` everywhere it’s needed. (Developers will get
immediate TypeScript and ESLint errors when they forget to do so.)
I’m doing this because I believe `import type` improves DX and makes
refactorings easier.
Let’s say you had a few imports like below. Can you tell which of these
imports will increase the bundle size? (Tip: it’s not all of them!)
```ts
// app/client/src/workers/Linting/utils.ts
import { Position } from "codemirror";
import { LintError as JSHintError, LintOptions } from "jshint";
import { get, isEmpty, isNumber, keys, last, set } from "lodash";
```
It’s pretty hard, right?
What about now?
```ts
// app/client/src/workers/Linting/utils.ts
import type { Position } from "codemirror";
import type { LintError as JSHintError, LintOptions } from "jshint";
import { get, isEmpty, isNumber, keys, last, set } from "lodash";
```
Now, it’s clear that only `lodash` will be bundled.
This helps developers to see which imports are problematic, but it
_also_ helps with refactorings. Now, if you want to see where
`codemirror` is bundled, you can just grep for `import \{.*\} from
"codemirror"` – and you won’t get any type-only imports.
This also helps (some) bundlers. Upon transpiling, TypeScript erases
type-only imports completely. In some environment (not ours), this makes
the bundle smaller, as the bundler doesn’t need to bundle type-only
imports anymore.
## Type of change
- Chore (housekeeping or task changes that don't impact user perception)
## How Has This Been Tested?
This was tested to not break the build.
### Test Plan
> Add Testsmith test cases links that relate to this PR
### Issues raised during DP testing
> Link issues raised during DP testing for better visiblity and tracking
(copy link from comments dropped on this PR)
## Checklist:
### Dev activity
- [x] My code follows the style guidelines of this project
- [ ] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [x] My changes generate no new warnings
- [ ] I have added tests that prove my fix is effective or that my
feature works
- [ ] New and existing unit tests pass locally with my changes
- [ ] PR is being merged under a feature flag
### QA activity:
- [ ] Test plan has been approved by relevant developers
- [ ] Test plan has been peer reviewed by QA
- [ ] Cypress test cases have been added and approved by either SDET or
manual QA
- [ ] Organized project review call with relevant stakeholders after
Round 1/2 of QA
- [ ] Added Test Plan Approved label after reveiwing all Cypress test
---------
Co-authored-by: Satish Gandham <hello@satishgandham.com>
Co-authored-by: Satish Gandham <satish.iitg@gmail.com>
2023-03-16 11:41:47 +00:00
|
|
|
.bp3-modal-widget,
|
|
|
|
|
.appsmith_widget_0 > .bp3-portal {
|
2021-05-19 07:20:00 +00:00
|
|
|
z-index: 2 !important;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/* Portals on the Modal widget */
|
|
|
|
|
.bp3-modal-widget .bp3-portal {
|
|
|
|
|
z-index: 21 !important;
|
|
|
|
|
}
|
2022-03-10 05:38:50 +00:00
|
|
|
|
2023-05-19 18:37:06 +00:00
|
|
|
.bp3-popover2-content {
|
|
|
|
|
background-color: var(--ads-v2-color-bg) !important;
|
|
|
|
|
border-radius: var(--ads-v2-border-radius) !important;
|
2023-03-04 07:25:54 +00:00
|
|
|
}
|
2022-03-10 05:38:50 +00:00
|
|
|
.bp3-overlay-backdrop {
|
|
|
|
|
background-color: rgba(16, 22, 26, 0.7) !important;
|
|
|
|
|
}
|
2022-12-14 08:13:43 +00:00
|
|
|
|
|
|
|
|
.bp3-overlay-zindex {
|
|
|
|
|
z-index: 20 !important;
|
chore: upgrade to prettier v2 + enforce import types (#21013)Co-authored-by: Satish Gandham <hello@satishgandham.com> Co-authored-by: Satish Gandham <satish.iitg@gmail.com>
## Description
This PR upgrades Prettier to v2 + enforces TypeScript’s [`import
type`](https://www.typescriptlang.org/docs/handbook/release-notes/typescript-3-8.html#type-only-imports-and-export)
syntax where applicable. It’s submitted as a separate PR so we can merge
it easily.
As a part of this PR, we reformat the codebase heavily:
- add `import type` everywhere where it’s required, and
- re-format the code to account for Prettier 2’s breaking changes:
https://prettier.io/blog/2020/03/21/2.0.0.html#breaking-changes
This PR is submitted against `release` to make sure all new code by team
members will adhere to new formatting standards, and we’ll have fewer
conflicts when merging `bundle-optimizations` into `release`. (I’ll
merge `release` back into `bundle-optimizations` once this PR is
merged.)
### Why is this needed?
This PR is needed because, for the Lodash optimization from
https://github.com/appsmithorg/appsmith/commit/7cbb12af886621256224be0c93e6a465dd710ad3,
we need to use `import type`. Otherwise, `babel-plugin-lodash` complains
that `LoDashStatic` is not a lodash function.
However, just using `import type` in the current codebase will give you
this:
<img width="962" alt="Screenshot 2023-03-08 at 17 45 59"
src="https://user-images.githubusercontent.com/2953267/223775744-407afa0c-e8b9-44a1-90f9-b879348da57f.png">
That’s because Prettier 1 can’t parse `import type` at all. To parse it,
we need to upgrade to Prettier 2.
### Why enforce `import type`?
Apart from just enabling `import type` support, this PR enforces
specifying `import type` everywhere it’s needed. (Developers will get
immediate TypeScript and ESLint errors when they forget to do so.)
I’m doing this because I believe `import type` improves DX and makes
refactorings easier.
Let’s say you had a few imports like below. Can you tell which of these
imports will increase the bundle size? (Tip: it’s not all of them!)
```ts
// app/client/src/workers/Linting/utils.ts
import { Position } from "codemirror";
import { LintError as JSHintError, LintOptions } from "jshint";
import { get, isEmpty, isNumber, keys, last, set } from "lodash";
```
It’s pretty hard, right?
What about now?
```ts
// app/client/src/workers/Linting/utils.ts
import type { Position } from "codemirror";
import type { LintError as JSHintError, LintOptions } from "jshint";
import { get, isEmpty, isNumber, keys, last, set } from "lodash";
```
Now, it’s clear that only `lodash` will be bundled.
This helps developers to see which imports are problematic, but it
_also_ helps with refactorings. Now, if you want to see where
`codemirror` is bundled, you can just grep for `import \{.*\} from
"codemirror"` – and you won’t get any type-only imports.
This also helps (some) bundlers. Upon transpiling, TypeScript erases
type-only imports completely. In some environment (not ours), this makes
the bundle smaller, as the bundler doesn’t need to bundle type-only
imports anymore.
## Type of change
- Chore (housekeeping or task changes that don't impact user perception)
## How Has This Been Tested?
This was tested to not break the build.
### Test Plan
> Add Testsmith test cases links that relate to this PR
### Issues raised during DP testing
> Link issues raised during DP testing for better visiblity and tracking
(copy link from comments dropped on this PR)
## Checklist:
### Dev activity
- [x] My code follows the style guidelines of this project
- [ ] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [x] My changes generate no new warnings
- [ ] I have added tests that prove my fix is effective or that my
feature works
- [ ] New and existing unit tests pass locally with my changes
- [ ] PR is being merged under a feature flag
### QA activity:
- [ ] Test plan has been approved by relevant developers
- [ ] Test plan has been peer reviewed by QA
- [ ] Cypress test cases have been added and approved by either SDET or
manual QA
- [ ] Organized project review call with relevant stakeholders after
Round 1/2 of QA
- [ ] Added Test Plan Approved label after reveiwing all Cypress test
---------
Co-authored-by: Satish Gandham <hello@satishgandham.com>
Co-authored-by: Satish Gandham <satish.iitg@gmail.com>
2023-03-16 11:41:47 +00:00
|
|
|
}
|
2023-05-19 18:37:06 +00:00
|
|
|
|
|
|
|
|
/** color picker input control */
|
|
|
|
|
.color-picker-input,
|
|
|
|
|
.color-picker-input > .bp3-popover-content {
|
|
|
|
|
border-radius: var(--ads-v2-border-radius) !important;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
.color-picker-input {
|
|
|
|
|
box-shadow: var(--ads-v2-shadow-popovers) !important;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
.icon-select-popover,
|
|
|
|
|
.icon-select-popover > .bp3-popover-content {
|
|
|
|
|
border-radius: var(--ads-v2-border-radius) !important;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
.icon-select-popover {
|
|
|
|
|
box-shadow: var(--ads-v2-shadow-popovers) !important;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
.error-menuitem {
|
|
|
|
|
color: var(--ads-v2-color-fg-error) !important;
|
|
|
|
|
}
|
|
|
|
|
.error-menuitem > .ads-v2-menu__menu-item-children {
|
|
|
|
|
color: var(--ads-v2-color-fg-error) !important;
|
|
|
|
|
}
|
2023-05-29 05:40:41 +00:00
|
|
|
|
|
|
|
|
.error-menuitem:hover:not([data-disabled]),
|
|
|
|
|
.error-menuitem:focus-visible {
|
2023-05-19 18:37:06 +00:00
|
|
|
background-color: var(--ads-v2-color-red-50) !important;
|
|
|
|
|
}
|
2023-05-29 05:40:41 +00:00
|
|
|
.error-menuitem:active:not([data-disabled]) {
|
2023-05-19 18:37:06 +00:00
|
|
|
background-color: var(--ads-v2-color-red-100) !important;
|
|
|
|
|
}
|
|
|
|
|
.menuitem-nohover:hover {
|
|
|
|
|
background-color: transparent !important;
|
|
|
|
|
cursor: default !important;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
.react-datepicker__children-container {
|
|
|
|
|
margin-top: -10px !important;
|
|
|
|
|
}
|
2023-05-25 12:38:51 +00:00
|
|
|
|
|
|
|
|
.reconnect-datasource-modal {
|
|
|
|
|
z-index: 9 !important;
|
|
|
|
|
}
|