2023-03-08 14:41:30 +00:00
import { ECMA_VERSION } from "@shared/ast" ;
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
import type { LintOptions } from "jshint" ;
2023-05-11 05:26:03 +00:00
import isEntityFunction from "./utils/isEntityFunction" ;
2023-03-08 14:41:30 +00:00
export const lintOptions = ( globalData : Record < string , boolean > ) = >
( {
indent : 2 ,
esversion : ECMA_VERSION ,
eqeqeq : false , // Not necessary to use ===
curly : false , // Blocks can be added without {}, eg if (x) return true
freeze : true , // Overriding inbuilt classes like Array is not allowed
undef : true , // Undefined variables should be reported as error
forin : false , // Doesn't require filtering for..in loops with obj.hasOwnProperty()
noempty : false , // Empty blocks are allowed
strict : false , // We won't force strict mode
unused : "strict" , // Unused variables are not allowed
asi : true , // Tolerate Automatic Semicolon Insertion (no semicolons)
boss : true , // Tolerate assignments where comparisons would be expected
evil : false , // Use of eval not allowed
funcscope : true , // Tolerate variable definition inside control statements
sub : true , // Don't force dot notation
expr : true , // suppresses warnings about the use of expressions where normally you would expect to see assignments or function calls
// environments
2024-04-18 13:19:15 +00:00
browser : false ,
2023-03-08 14:41:30 +00:00
worker : true ,
mocha : false ,
// global values
globals : globalData ,
loopfunc : true ,
2023-10-11 07:14:38 +00:00
} ) as LintOptions ;
2023-03-08 14:41:30 +00:00
export const JS_OBJECT_START_STATEMENT = "export default" ;
export const INVALID_JSOBJECT_START_STATEMENT = ` JSObject must start with ' ${ JS_OBJECT_START_STATEMENT } ' ` ;
2023-04-03 10:41:15 +00:00
export const INVALID_JSOBJECT_START_STATEMENT_ERROR_CODE =
"INVALID_JSOBJECT_START_STATEMENT_ERROR_CODE" ;
2023-03-08 14:41:30 +00:00
// https://github.com/jshint/jshint/blob/d3d84ae1695359aef077ddb143f4be98001343b4/src/messages.js#L204
export const IDENTIFIER_NOT_DEFINED_LINT_ERROR_CODE = "W117" ;
// For these error types, we want to show a warning
// All messages can be found here => https://github.com/jshint/jshint/blob/2.9.5/src/messages.js
export const WARNING_LINT_ERRORS = {
W098 : "'{a}' is defined but never used." ,
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
W014 : "Misleading line break before '{a}'; readers may interpret this as an expression boundary." ,
2023-04-03 10:41:15 +00:00
ASYNC_FUNCTION_BOUND_TO_SYNC_FIELD :
"Cannot execute async code on functions bound to data fields" ,
2024-05-02 12:18:53 +00:00
ACTION_MODAL_STRING : 'Use Modal1.name instead of "Modal" as a string' ,
2023-03-08 14:41:30 +00:00
} ;
2023-04-03 10:41:15 +00:00
export function asyncActionInSyncFieldLintMessage ( isJsObject = false ) {
return isJsObject
? ` Cannot execute async code on functions bound to data fields `
: ` Data fields cannot execute async code ` ;
2023-03-08 14:41:30 +00:00
}
/ * * T h e s e e r r o r s s h o u l d b e o v e r l o o k e d
* E041 = > Unrecoverable syntax error .
* W032 = > Unnecessary semicolon .
* /
export const IGNORED_LINT_ERRORS = [ "E041" , "W032" ] ;
export const SUPPORTED_WEB_APIS = {
console : true ,
crypto : true ,
2024-05-10 06:00:07 +00:00
fetch : true ,
2023-03-08 14:41:30 +00:00
} ;
export enum CustomLintErrorCode {
INVALID_ENTITY_PROPERTY = "INVALID_ENTITY_PROPERTY" ,
2023-04-03 10:41:15 +00:00
ASYNC_FUNCTION_BOUND_TO_SYNC_FIELD = "ASYNC_FUNCTION_BOUND_TO_SYNC_FIELD" ,
2023-09-29 12:30:23 +00:00
// ButtonWidget.text = "test"
INVALID_WIDGET_PROPERTY_SETTER = "INVALID_WIDGET_PROPERTY_SETTER" ,
// appsmith.store.value = "test"
INVALID_APPSMITH_STORE_PROPERTY_SETTER = "INVALID_APPSMITH_STORE_PROPERTY_SETTER" ,
2024-05-02 12:18:53 +00:00
// showModal("Modal1")
ACTION_MODAL_STRING = "ACTION_MODAL_STRING" ,
2023-03-08 14:41:30 +00:00
}
2023-04-03 10:41:15 +00:00
2023-03-08 14:41:30 +00:00
export const CUSTOM_LINT_ERRORS : Record <
CustomLintErrorCode ,
( . . . args : any [ ] ) = > string
> = {
[ CustomLintErrorCode . INVALID_ENTITY_PROPERTY ] : (
entityName : string ,
propertyName : string ,
2023-04-03 10:41:15 +00:00
entity : unknown ,
isJsObject : boolean ,
) = >
2023-07-08 14:07:26 +00:00
isEntityFunction ( entity , propertyName , entityName )
2023-04-03 10:41:15 +00:00
? asyncActionInSyncFieldLintMessage ( isJsObject )
: ` " ${ propertyName } " doesn't exist in ${ entityName } ` ,
[ CustomLintErrorCode . ASYNC_FUNCTION_BOUND_TO_SYNC_FIELD ] : (
dataFieldBindings : string [ ] ,
fullName : string ,
isMarkedAsync : boolean ,
) = > {
const hasMultipleBindings = dataFieldBindings . length > 1 ;
const bindings = dataFieldBindings . join ( " , " ) ;
return isMarkedAsync
? ` Cannot bind async functions to data fields. Convert this to a sync function or remove references to " ${ fullName } " on the following data ${
hasMultipleBindings ? "fields" : "field"
} : $ { bindings } `
: ` Functions bound to data fields cannot execute async code. Remove async statements highlighted below or remove references to " ${ fullName } " on the following data ${
hasMultipleBindings ? "fields" : "field"
} : $ { bindings } ` ;
} ,
2023-09-29 12:30:23 +00:00
[ CustomLintErrorCode . INVALID_WIDGET_PROPERTY_SETTER ] : (
methodName : string ,
objectName : string ,
propertyName : string ,
isValidProperty : boolean ,
) = > {
const suggestionSentence = methodName
? ` Use ${ methodName } (value) instead. `
: ` Use ${ objectName } setter method instead. ` ;
const lintErrorMessage = ! isValidProperty
? ` ${ objectName } doesn't have a property named ${ propertyName } `
: ` Direct mutation of widget properties is not supported. ${ suggestionSentence } ` ;
return lintErrorMessage ;
} ,
[ CustomLintErrorCode . INVALID_APPSMITH_STORE_PROPERTY_SETTER ] : ( ) = > {
return "Use storeValue() method to modify the store" ;
} ,
2024-05-02 12:18:53 +00:00
[ CustomLintErrorCode . ACTION_MODAL_STRING ] : ( modalName : string ) = > {
return ` Use ${ modalName } .name instead of " ${ modalName } " as a string ` ;
} ,
2023-03-08 14:41:30 +00:00
} ;