2022-12-01 04:55:57 +00:00
|
|
|
import React from "react";
|
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 { ControlProps } from "./BaseControl";
|
|
|
|
|
import BaseControl from "./BaseControl";
|
2022-12-01 04:55:57 +00:00
|
|
|
import { StyledDynamicInput } from "./StyledControls";
|
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 { CodeEditorExpected } from "components/editorComponents/CodeEditor";
|
|
|
|
|
import CodeEditor from "components/editorComponents/CodeEditor";
|
|
|
|
|
import type { EditorTheme } from "components/editorComponents/CodeEditor/EditorConfig";
|
2022-12-01 04:55:57 +00:00
|
|
|
import {
|
|
|
|
|
EditorModes,
|
|
|
|
|
EditorSize,
|
|
|
|
|
TabBehaviour,
|
|
|
|
|
} from "components/editorComponents/CodeEditor/EditorConfig";
|
|
|
|
|
import { isDynamicValue } from "utils/DynamicBindingUtils";
|
|
|
|
|
import styled from "styled-components";
|
|
|
|
|
import { isString } from "utils/helpers";
|
|
|
|
|
import {
|
|
|
|
|
JSToString,
|
|
|
|
|
stringToJS,
|
|
|
|
|
} from "components/editorComponents/ActionCreator/utils";
|
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 { AdditionalDynamicDataTree } from "utils/autocomplete/customTreeTypeDefCreator";
|
|
|
|
|
import type { ColumnProperties } from "widgets/TableWidgetV2/component/Constants";
|
2022-12-30 10:52:11 +00:00
|
|
|
import { getUniqueKeysFromSourceData } from "widgets/MenuButtonWidget/widget/helper";
|
2022-12-01 04:55:57 +00:00
|
|
|
|
|
|
|
|
const PromptMessage = styled.span`
|
|
|
|
|
line-height: 17px;
|
|
|
|
|
`;
|
|
|
|
|
const CurlyBraces = styled.span`
|
|
|
|
|
color: ${(props) => props.theme.colors.codeMirror.background.hoverState};
|
|
|
|
|
background-color: #575757;
|
|
|
|
|
border-radius: 2px;
|
|
|
|
|
padding: 2px;
|
|
|
|
|
margin: 0px 2px;
|
|
|
|
|
font-size: 10px;
|
|
|
|
|
`;
|
|
|
|
|
|
|
|
|
|
type InputTextProp = {
|
|
|
|
|
label: string;
|
|
|
|
|
value: string;
|
|
|
|
|
onChange: (event: React.ChangeEvent<HTMLTextAreaElement> | string) => void;
|
|
|
|
|
evaluatedValue?: any;
|
|
|
|
|
expected?: CodeEditorExpected;
|
|
|
|
|
placeholder?: string;
|
|
|
|
|
dataTreePath?: string;
|
|
|
|
|
additionalDynamicData: AdditionalDynamicDataTree;
|
|
|
|
|
theme: EditorTheme;
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
function InputText(props: InputTextProp) {
|
|
|
|
|
const {
|
|
|
|
|
additionalDynamicData,
|
|
|
|
|
dataTreePath,
|
|
|
|
|
evaluatedValue,
|
|
|
|
|
expected,
|
|
|
|
|
onChange,
|
|
|
|
|
placeholder,
|
|
|
|
|
theme,
|
|
|
|
|
value,
|
|
|
|
|
} = props;
|
|
|
|
|
return (
|
|
|
|
|
<StyledDynamicInput>
|
|
|
|
|
<CodeEditor
|
|
|
|
|
additionalDynamicData={additionalDynamicData}
|
|
|
|
|
dataTreePath={dataTreePath}
|
|
|
|
|
evaluatedValue={evaluatedValue}
|
|
|
|
|
expected={expected}
|
|
|
|
|
input={{
|
|
|
|
|
value: value,
|
|
|
|
|
onChange: onChange,
|
|
|
|
|
}}
|
|
|
|
|
mode={EditorModes.TEXT_WITH_BINDING}
|
|
|
|
|
placeholder={placeholder}
|
|
|
|
|
promptMessage={
|
|
|
|
|
<PromptMessage>
|
|
|
|
|
Access the current item using <CurlyBraces>{"{{"}</CurlyBraces>
|
|
|
|
|
currentItem
|
|
|
|
|
<CurlyBraces>{"}}"}</CurlyBraces>
|
|
|
|
|
</PromptMessage>
|
|
|
|
|
}
|
|
|
|
|
size={EditorSize.EXTENDED}
|
|
|
|
|
tabBehaviour={TabBehaviour.INDENT}
|
|
|
|
|
theme={theme}
|
|
|
|
|
/>
|
|
|
|
|
</StyledDynamicInput>
|
|
|
|
|
);
|
|
|
|
|
}
|
|
|
|
|
|
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
|
|
|
class MenuButtonDynamicItemsControl extends BaseControl<MenuButtonDynamicItemsControlProps> {
|
2022-12-01 04:55:57 +00:00
|
|
|
render() {
|
|
|
|
|
const {
|
|
|
|
|
dataTreePath,
|
|
|
|
|
defaultValue,
|
|
|
|
|
expected,
|
|
|
|
|
label,
|
|
|
|
|
propertyValue,
|
|
|
|
|
theme,
|
2022-12-30 10:52:11 +00:00
|
|
|
widgetProperties,
|
2022-12-01 04:55:57 +00:00
|
|
|
} = this.props;
|
2022-12-30 10:52:11 +00:00
|
|
|
const widgetName = widgetProperties.widgetName;
|
|
|
|
|
const widgetType = widgetProperties.type;
|
2022-12-01 04:55:57 +00:00
|
|
|
const value =
|
|
|
|
|
propertyValue && isDynamicValue(propertyValue)
|
|
|
|
|
? MenuButtonDynamicItemsControl.getInputComputedValue(
|
|
|
|
|
propertyValue,
|
2022-12-30 10:52:11 +00:00
|
|
|
widgetName,
|
|
|
|
|
widgetType,
|
|
|
|
|
widgetProperties.primaryColumns,
|
2022-12-01 04:55:57 +00:00
|
|
|
)
|
|
|
|
|
: propertyValue
|
|
|
|
|
? propertyValue
|
|
|
|
|
: defaultValue;
|
2022-12-30 10:52:11 +00:00
|
|
|
let sourceData;
|
|
|
|
|
|
|
|
|
|
if (widgetType === "TABLE_WIDGET_V2") {
|
|
|
|
|
sourceData =
|
|
|
|
|
widgetProperties?.__evaluation__?.evaluatedValues?.primaryColumns?.[
|
|
|
|
|
`${Object.keys(widgetProperties.primaryColumns)[0]}`
|
|
|
|
|
]?.sourceData;
|
|
|
|
|
} else if (widgetType === "MENU_BUTTON_WIDGET") {
|
|
|
|
|
sourceData =
|
|
|
|
|
widgetProperties?.__evaluation__?.evaluatedValues?.sourceData;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
const keys = getUniqueKeysFromSourceData(sourceData);
|
2022-12-01 04:55:57 +00:00
|
|
|
const currentItem: { [key: string]: any } = {};
|
|
|
|
|
|
|
|
|
|
Object.values(keys).forEach((key) => {
|
|
|
|
|
currentItem[key as keyof typeof currentItem] = undefined;
|
|
|
|
|
});
|
|
|
|
|
|
|
|
|
|
// Load default value in evaluated value
|
|
|
|
|
if (value && !propertyValue) {
|
|
|
|
|
this.onTextChange(value);
|
|
|
|
|
}
|
2022-12-30 10:52:11 +00:00
|
|
|
|
2022-12-01 04:55:57 +00:00
|
|
|
return (
|
|
|
|
|
<InputText
|
|
|
|
|
additionalDynamicData={{
|
|
|
|
|
currentItem,
|
|
|
|
|
currentIndex: -1,
|
|
|
|
|
}}
|
|
|
|
|
dataTreePath={dataTreePath}
|
|
|
|
|
expected={expected}
|
|
|
|
|
label={label}
|
|
|
|
|
onChange={this.onTextChange}
|
|
|
|
|
theme={theme}
|
|
|
|
|
value={value}
|
|
|
|
|
/>
|
|
|
|
|
);
|
|
|
|
|
}
|
|
|
|
|
|
2022-12-30 10:52:11 +00:00
|
|
|
static getBindingPrefix = (
|
|
|
|
|
widgetName: string,
|
|
|
|
|
widgetType?: string,
|
|
|
|
|
primaryColumns?: Record<string, ColumnProperties>,
|
|
|
|
|
) => {
|
|
|
|
|
if (widgetType === "TABLE_WIDGET_V2" && primaryColumns) {
|
|
|
|
|
const columnName = Object.keys(primaryColumns)?.[0];
|
|
|
|
|
|
|
|
|
|
return `{{${widgetName}.processedTableData.map((currentRow, currentRowIndex) => {
|
|
|
|
|
let primaryColumnData = [];
|
|
|
|
|
|
|
|
|
|
if (${widgetName}.primaryColumns.${columnName}.sourceData[currentRowIndex].length) {
|
|
|
|
|
primaryColumnData = ${widgetName}.primaryColumns.${columnName}.sourceData[currentRowIndex];
|
|
|
|
|
} else if (${widgetName}.primaryColumns.${columnName}.sourceData.length) {
|
|
|
|
|
primaryColumnData = ${widgetName}.primaryColumns.${columnName}.sourceData;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
return primaryColumnData.map((currentItem, currentIndex) => `;
|
|
|
|
|
} else {
|
|
|
|
|
return `{{${widgetName}.sourceData.map((currentItem, currentIndex) => ( `;
|
|
|
|
|
}
|
2022-12-01 04:55:57 +00:00
|
|
|
};
|
|
|
|
|
|
2022-12-30 10:52:11 +00:00
|
|
|
static getBindingSuffix = (widgetType?: string) =>
|
|
|
|
|
widgetType === "TABLE_WIDGET_V2" ? `);});}}` : `))}}`;
|
2022-12-01 04:55:57 +00:00
|
|
|
|
|
|
|
|
static getInputComputedValue = (
|
|
|
|
|
propertyValue: string,
|
2022-12-30 10:52:11 +00:00
|
|
|
widgetName: string,
|
|
|
|
|
widgetType?: string,
|
|
|
|
|
primaryColumns?: Record<string, ColumnProperties>,
|
2022-12-01 04:55:57 +00:00
|
|
|
) => {
|
2022-12-30 10:52:11 +00:00
|
|
|
if (
|
|
|
|
|
!propertyValue.includes(
|
|
|
|
|
this.getBindingPrefix(widgetName, widgetType, primaryColumns),
|
|
|
|
|
)
|
|
|
|
|
) {
|
2022-12-01 04:55:57 +00:00
|
|
|
return propertyValue;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
const value = `${propertyValue.substring(
|
2022-12-30 10:52:11 +00:00
|
|
|
this.getBindingPrefix(widgetName, widgetType, primaryColumns).length,
|
|
|
|
|
propertyValue.length - this.getBindingSuffix(widgetType).length,
|
2022-12-01 04:55:57 +00:00
|
|
|
)}`;
|
|
|
|
|
const stringValue = JSToString(value);
|
|
|
|
|
|
|
|
|
|
return stringValue;
|
|
|
|
|
};
|
|
|
|
|
|
2022-12-30 10:52:11 +00:00
|
|
|
getComputedValue = (
|
|
|
|
|
value: string,
|
|
|
|
|
widgetName: string,
|
|
|
|
|
widgetType?: string,
|
|
|
|
|
primaryColumns?: Record<string, ColumnProperties>,
|
|
|
|
|
) => {
|
2022-12-01 04:55:57 +00:00
|
|
|
if (!isDynamicValue(value)) {
|
|
|
|
|
return value;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
const stringToEvaluate = stringToJS(value);
|
|
|
|
|
|
|
|
|
|
if (stringToEvaluate === "") {
|
|
|
|
|
return stringToEvaluate;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
return `${MenuButtonDynamicItemsControl.getBindingPrefix(
|
2022-12-30 10:52:11 +00:00
|
|
|
widgetName,
|
|
|
|
|
widgetType,
|
|
|
|
|
primaryColumns,
|
|
|
|
|
)}${stringToEvaluate}${MenuButtonDynamicItemsControl.getBindingSuffix(
|
|
|
|
|
widgetType,
|
|
|
|
|
)}`;
|
2022-12-01 04:55:57 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
|
|
onTextChange = (event: React.ChangeEvent<HTMLTextAreaElement> | string) => {
|
|
|
|
|
let value = "";
|
|
|
|
|
if (typeof event !== "string") {
|
|
|
|
|
value = event.target?.value;
|
|
|
|
|
} else {
|
|
|
|
|
value = event;
|
|
|
|
|
}
|
|
|
|
|
if (isString(value)) {
|
|
|
|
|
const output = this.getComputedValue(
|
|
|
|
|
value,
|
|
|
|
|
this.props.widgetProperties.widgetName,
|
2022-12-30 10:52:11 +00:00
|
|
|
this.props.widgetProperties.type,
|
|
|
|
|
this.props.widgetProperties.primaryColumns,
|
2022-12-01 04:55:57 +00:00
|
|
|
);
|
|
|
|
|
|
|
|
|
|
this.updateProperty(this.props.propertyName, output);
|
|
|
|
|
} else {
|
|
|
|
|
this.updateProperty(this.props.propertyName, value);
|
|
|
|
|
}
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
static getControlType() {
|
|
|
|
|
return "MENU_BUTTON_DYNAMIC_ITEMS";
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
export interface MenuButtonDynamicItemsControlProps extends ControlProps {
|
|
|
|
|
defaultValue?: string;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
export default MenuButtonDynamicItemsControl;
|