2020-02-18 10:41:52 +00:00
|
|
|
import { createSelector } from "reselect";
|
2021-03-30 05:29:03 +00:00
|
|
|
import {
|
|
|
|
|
getActionsForCurrentPage,
|
|
|
|
|
getAppData,
|
2021-04-26 05:41:32 +00:00
|
|
|
getPluginDependencyConfig,
|
2021-03-30 05:29:03 +00:00
|
|
|
getPluginEditorConfigs,
|
2021-09-08 17:32:22 +00:00
|
|
|
getJSCollectionsForCurrentPage,
|
2021-03-30 05:29:03 +00:00
|
|
|
} from "./entitiesSelector";
|
2023-03-20 11:04:02 +00:00
|
|
|
import type { DataTree, WidgetEntity } from "entities/DataTree/dataTreeFactory";
|
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 { DataTreeFactory } from "entities/DataTree/dataTreeFactory";
|
2023-02-14 16:07:31 +00:00
|
|
|
import {
|
|
|
|
|
getMetaWidgets,
|
|
|
|
|
getWidgetsForEval,
|
|
|
|
|
getWidgetsMeta,
|
|
|
|
|
} from "sagas/selectors";
|
2020-04-01 08:09:57 +00:00
|
|
|
import "url-search-params-polyfill";
|
2020-04-20 05:42:46 +00:00
|
|
|
import { getPageList } from "./appViewSelectors";
|
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 { AppState } from "@appsmith/reducers";
|
2022-05-04 09:45:57 +00:00
|
|
|
import { getSelectedAppThemeProperties } from "./appThemingSelectors";
|
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 { LoadingEntitiesState } from "reducers/evaluationReducers/loadingEntitiesReducer";
|
2023-06-05 03:54:10 +00:00
|
|
|
import _, { get } from "lodash";
|
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 { EvaluationError } from "utils/DynamicBindingUtils";
|
|
|
|
|
import { getEvalErrorPath } from "utils/DynamicBindingUtils";
|
2023-03-20 11:04:02 +00:00
|
|
|
import ConfigTreeActions from "utils/configTree";
|
2023-06-05 03:54:10 +00:00
|
|
|
import { DATATREE_INTERNAL_KEYWORDS } from "constants/WidgetValidation";
|
2020-04-01 08:09:57 +00:00
|
|
|
|
2020-09-24 04:47:37 +00:00
|
|
|
export const getUnevaluatedDataTree = createSelector(
|
|
|
|
|
getActionsForCurrentPage,
|
2021-09-08 17:32:22 +00:00
|
|
|
getJSCollectionsForCurrentPage,
|
2022-12-02 12:45:11 +00:00
|
|
|
getWidgetsForEval,
|
2020-09-24 04:47:37 +00:00
|
|
|
getWidgetsMeta,
|
|
|
|
|
getPageList,
|
|
|
|
|
getAppData,
|
2021-03-30 05:29:03 +00:00
|
|
|
getPluginEditorConfigs,
|
2021-04-26 05:41:32 +00:00
|
|
|
getPluginDependencyConfig,
|
2022-05-04 09:45:57 +00:00
|
|
|
getSelectedAppThemeProperties,
|
2023-02-14 16:07:31 +00:00
|
|
|
getMetaWidgets,
|
2021-04-26 05:41:32 +00:00
|
|
|
(
|
|
|
|
|
actions,
|
2021-09-08 17:32:22 +00:00
|
|
|
jsActions,
|
2021-04-26 05:41:32 +00:00
|
|
|
widgets,
|
|
|
|
|
widgetsMeta,
|
|
|
|
|
pageListPayload,
|
|
|
|
|
appData,
|
|
|
|
|
editorConfigs,
|
|
|
|
|
pluginDependencyConfig,
|
2022-05-04 09:45:57 +00:00
|
|
|
selectedAppThemeProperty,
|
2023-02-14 16:07:31 +00:00
|
|
|
metaWidgets,
|
2021-04-26 05:41:32 +00:00
|
|
|
) => {
|
2020-09-24 04:47:37 +00:00
|
|
|
const pageList = pageListPayload || [];
|
2021-03-31 07:40:59 +00:00
|
|
|
return DataTreeFactory.create({
|
2020-10-21 04:25:32 +00:00
|
|
|
actions,
|
2021-09-08 17:32:22 +00:00
|
|
|
jsActions,
|
2020-10-21 04:25:32 +00:00
|
|
|
widgets,
|
|
|
|
|
widgetsMeta,
|
|
|
|
|
pageList,
|
|
|
|
|
appData,
|
2021-03-30 05:29:03 +00:00
|
|
|
editorConfigs,
|
2021-04-26 05:41:32 +00:00
|
|
|
pluginDependencyConfig,
|
2022-05-04 09:45:57 +00:00
|
|
|
theme: selectedAppThemeProperty,
|
2023-02-14 16:07:31 +00:00
|
|
|
metaWidgets,
|
2020-10-21 04:25:32 +00:00
|
|
|
});
|
2020-09-24 04:47:37 +00:00
|
|
|
},
|
|
|
|
|
);
|
2020-02-18 10:41:52 +00:00
|
|
|
|
2021-01-04 10:16:08 +00:00
|
|
|
export const getEvaluationInverseDependencyMap = (state: AppState) =>
|
|
|
|
|
state.evaluations.dependencies.inverseDependencyMap;
|
|
|
|
|
|
2021-01-14 14:37:21 +00:00
|
|
|
export const getLoadingEntities = (state: AppState) =>
|
|
|
|
|
state.evaluations.loadingEntities;
|
|
|
|
|
|
2022-08-19 10:10:36 +00:00
|
|
|
export const getIsWidgetLoading = createSelector(
|
|
|
|
|
[getLoadingEntities, (_state: AppState, widgetName: string) => widgetName],
|
|
|
|
|
(loadingEntities: LoadingEntitiesState, widgetName: string) =>
|
|
|
|
|
loadingEntities.has(widgetName),
|
|
|
|
|
);
|
|
|
|
|
|
2020-11-23 09:27:00 +00:00
|
|
|
/**
|
|
|
|
|
* returns evaluation tree object
|
|
|
|
|
*
|
|
|
|
|
* @param state
|
|
|
|
|
*/
|
2021-08-25 05:00:31 +00:00
|
|
|
export const getDataTree = (state: AppState): DataTree =>
|
|
|
|
|
state.evaluations.tree;
|
2020-07-06 13:35:31 +00:00
|
|
|
|
2023-03-20 11:04:02 +00:00
|
|
|
export const getConfigTree = (): any => {
|
|
|
|
|
return ConfigTreeActions.getConfigTree();
|
|
|
|
|
};
|
|
|
|
|
|
2022-08-19 10:10:36 +00:00
|
|
|
export const getWidgetEvalValues = createSelector(
|
|
|
|
|
[getDataTree, (_state: AppState, widgetName: string) => widgetName],
|
2023-03-20 11:04:02 +00:00
|
|
|
(tree: DataTree, widgetName: string) => tree[widgetName] as WidgetEntity,
|
2022-08-19 10:10:36 +00:00
|
|
|
);
|
|
|
|
|
|
2020-02-18 10:41:52 +00:00
|
|
|
// For autocomplete. Use actions cached responses if
|
|
|
|
|
// there isn't a response already
|
2020-02-26 12:44:56 +00:00
|
|
|
export const getDataTreeForAutocomplete = createSelector(
|
2020-10-21 04:25:32 +00:00
|
|
|
getDataTree,
|
2022-11-18 10:23:24 +00:00
|
|
|
(tree: DataTree) => {
|
2023-06-05 03:54:10 +00:00
|
|
|
return _.omit(tree, Object.keys(DATATREE_INTERNAL_KEYWORDS));
|
2020-02-18 10:41:52 +00:00
|
|
|
},
|
2020-02-26 12:44:56 +00:00
|
|
|
);
|
2023-04-24 06:00:59 +00:00
|
|
|
|
2022-11-03 09:23:15 +00:00
|
|
|
export const getPathEvalErrors = createSelector(
|
|
|
|
|
[
|
|
|
|
|
getDataTreeForAutocomplete,
|
|
|
|
|
(_: unknown, dataTreePath: string) => dataTreePath,
|
|
|
|
|
],
|
|
|
|
|
(dataTree: DataTree, dataTreePath: string) =>
|
|
|
|
|
get(dataTree, getEvalErrorPath(dataTreePath), []) as EvaluationError[],
|
|
|
|
|
);
|