2022-08-04 05:40:44 +00:00
|
|
|
import { createReducer } from "utils/ReducerUtils";
|
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 { ReduxAction } from "@appsmith/constants/ReduxActionConstants";
|
2019-11-13 07:34:59 +00:00
|
|
|
import {
|
|
|
|
|
ReduxActionTypes,
|
|
|
|
|
ReduxActionErrorTypes,
|
2022-04-12 10:50:01 +00:00
|
|
|
} from "@appsmith/constants/ReduxActionConstants";
|
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 { Action } from "entities/Action";
|
|
|
|
|
import type { UpdateActionPropertyActionPayload } from "actions/pluginActionActions";
|
2019-11-13 07:34:59 +00:00
|
|
|
|
|
|
|
|
const initialState: ApiPaneReduxState = {
|
2020-06-20 05:29:30 +00:00
|
|
|
isCreating: false,
|
2019-11-13 07:34:59 +00:00
|
|
|
isFetching: false,
|
2019-12-11 15:14:38 +00:00
|
|
|
isRunning: {},
|
|
|
|
|
isSaving: {},
|
|
|
|
|
isDeleting: {},
|
2020-07-03 08:58:58 +00:00
|
|
|
isDirty: {},
|
2020-04-28 10:47:59 +00:00
|
|
|
currentCategory: "",
|
2020-05-07 07:56:37 +00:00
|
|
|
extraformData: {},
|
2022-10-17 15:16:38 +00:00
|
|
|
selectedConfigTabIndex: 0,
|
|
|
|
|
selectedResponseTab: "",
|
2019-11-13 07:34:59 +00:00
|
|
|
};
|
2020-06-18 14:16:49 +00:00
|
|
|
|
2019-11-13 07:34:59 +00:00
|
|
|
export interface ApiPaneReduxState {
|
Feature/entity browse (#220)
# New Feature: Entity Explorer
- Entities are actions (apis and queries), datasources, pages, and widgets
- With this new feature, all entities in the application will be available
to view in the new entity explorer sidebar
- All existing application features from the api sidebar, query sidebar, datasource sidebar and pages sidebar
now are avialable on the entity explorer sidebar
- Users are now able to quickly switch to any entity in the application from the entity explorer sidebar.
- Users can also search all entities in the application from the new sidebar. Use cmd + f or ctrl + f to focus on the search input
- Users can rename entities from the new sidebar
- Users can also perform contextual actions on these entities like set a page as home page, copy/move actions, delete entity, etc from the context menu available alongside the entities in the sidebar
- Users can view the properties of the entities in the sidebar, as well as copy bindings to use in the application.
2020-08-10 08:52:45 +00:00
|
|
|
isCreating: boolean; // RR
|
|
|
|
|
isFetching: boolean; // RR
|
2019-12-11 15:14:38 +00:00
|
|
|
isRunning: Record<string, boolean>;
|
Feature/entity browse (#220)
# New Feature: Entity Explorer
- Entities are actions (apis and queries), datasources, pages, and widgets
- With this new feature, all entities in the application will be available
to view in the new entity explorer sidebar
- All existing application features from the api sidebar, query sidebar, datasource sidebar and pages sidebar
now are avialable on the entity explorer sidebar
- Users are now able to quickly switch to any entity in the application from the entity explorer sidebar.
- Users can also search all entities in the application from the new sidebar. Use cmd + f or ctrl + f to focus on the search input
- Users can rename entities from the new sidebar
- Users can also perform contextual actions on these entities like set a page as home page, copy/move actions, delete entity, etc from the context menu available alongside the entities in the sidebar
- Users can view the properties of the entities in the sidebar, as well as copy bindings to use in the application.
2020-08-10 08:52:45 +00:00
|
|
|
isSaving: Record<string, boolean>; // RN
|
2019-12-11 15:14:38 +00:00
|
|
|
isDeleting: Record<string, boolean>;
|
2020-07-03 08:58:58 +00:00
|
|
|
isDirty: Record<string, boolean>;
|
2020-04-28 10:47:59 +00:00
|
|
|
currentCategory: string;
|
2020-05-07 07:56:37 +00:00
|
|
|
extraformData: Record<string, any>;
|
2022-10-17 15:16:38 +00:00
|
|
|
selectedConfigTabIndex: number;
|
|
|
|
|
selectedResponseTab: string;
|
2023-05-19 18:37:06 +00:00
|
|
|
selectedRightPaneTab?: string;
|
2019-11-13 07:34:59 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
const apiPaneReducer = createReducer(initialState, {
|
|
|
|
|
[ReduxActionTypes.FETCH_ACTIONS_INIT]: (state: ApiPaneReduxState) => ({
|
|
|
|
|
...state,
|
|
|
|
|
isFetching: true,
|
|
|
|
|
}),
|
|
|
|
|
[ReduxActionTypes.FETCH_ACTIONS_SUCCESS]: (state: ApiPaneReduxState) => ({
|
|
|
|
|
...state,
|
|
|
|
|
isFetching: false,
|
|
|
|
|
}),
|
|
|
|
|
[ReduxActionErrorTypes.FETCH_ACTIONS_ERROR]: (state: ApiPaneReduxState) => ({
|
|
|
|
|
...state,
|
|
|
|
|
isFetching: false,
|
|
|
|
|
}),
|
2020-06-20 05:29:30 +00:00
|
|
|
[ReduxActionTypes.CREATE_ACTION_INIT]: (
|
|
|
|
|
state: ApiPaneReduxState,
|
|
|
|
|
): ApiPaneReduxState => ({
|
|
|
|
|
...state,
|
|
|
|
|
isCreating: true,
|
|
|
|
|
}),
|
|
|
|
|
[ReduxActionTypes.CREATE_ACTION_SUCCESS]: (
|
|
|
|
|
state: ApiPaneReduxState,
|
|
|
|
|
): ApiPaneReduxState => ({
|
|
|
|
|
...state,
|
|
|
|
|
isCreating: false,
|
|
|
|
|
}),
|
|
|
|
|
[ReduxActionErrorTypes.CREATE_ACTION_ERROR]: (
|
|
|
|
|
state: ApiPaneReduxState,
|
|
|
|
|
): ApiPaneReduxState => ({
|
|
|
|
|
...state,
|
|
|
|
|
isCreating: false,
|
|
|
|
|
}),
|
2020-07-03 08:58:58 +00:00
|
|
|
[ReduxActionTypes.RUN_ACTION_REQUEST]: (
|
2019-12-11 15:14:38 +00:00
|
|
|
state: ApiPaneReduxState,
|
2020-02-13 11:38:34 +00:00
|
|
|
action: ReduxAction<{ id: string }>,
|
2019-12-11 15:14:38 +00:00
|
|
|
) => ({
|
2019-11-13 07:34:59 +00:00
|
|
|
...state,
|
2019-12-11 15:14:38 +00:00
|
|
|
isRunning: {
|
|
|
|
|
...state.isRunning,
|
2020-02-13 11:38:34 +00:00
|
|
|
[action.payload.id]: true,
|
2019-12-11 15:14:38 +00:00
|
|
|
},
|
2019-11-13 07:34:59 +00:00
|
|
|
}),
|
2020-07-03 08:58:58 +00:00
|
|
|
[ReduxActionTypes.RUN_ACTION_SUCCESS]: (
|
2019-12-11 15:14:38 +00:00
|
|
|
state: ApiPaneReduxState,
|
|
|
|
|
action: ReduxAction<{ [id: string]: any }>,
|
|
|
|
|
) => {
|
|
|
|
|
const actionId = Object.keys(action.payload)[0];
|
|
|
|
|
return {
|
|
|
|
|
...state,
|
|
|
|
|
isRunning: {
|
|
|
|
|
...state.isRunning,
|
|
|
|
|
[actionId]: false,
|
|
|
|
|
},
|
|
|
|
|
};
|
|
|
|
|
},
|
2020-07-03 08:58:58 +00:00
|
|
|
[ReduxActionErrorTypes.RUN_ACTION_ERROR]: (
|
2019-12-11 15:14:38 +00:00
|
|
|
state: ApiPaneReduxState,
|
|
|
|
|
action: ReduxAction<{ id: string }>,
|
|
|
|
|
) => ({
|
2019-11-13 07:34:59 +00:00
|
|
|
...state,
|
2019-12-11 15:14:38 +00:00
|
|
|
isRunning: {
|
|
|
|
|
...state.isRunning,
|
|
|
|
|
[action.payload.id]: false,
|
|
|
|
|
},
|
2019-11-13 07:34:59 +00:00
|
|
|
}),
|
2021-12-14 12:37:42 +00:00
|
|
|
[ReduxActionTypes.RUN_ACTION_CANCELLED]: (
|
|
|
|
|
state: ApiPaneReduxState,
|
|
|
|
|
action: ReduxAction<{ id: string }>,
|
|
|
|
|
): ApiPaneReduxState => ({
|
|
|
|
|
...state,
|
|
|
|
|
isRunning: {
|
|
|
|
|
...state.isRunning,
|
|
|
|
|
[action.payload.id]: false,
|
|
|
|
|
},
|
|
|
|
|
}),
|
2020-07-03 08:58:58 +00:00
|
|
|
[ReduxActionTypes.UPDATE_ACTION_PROPERTY]: (
|
|
|
|
|
state: ApiPaneReduxState,
|
|
|
|
|
action: ReduxAction<UpdateActionPropertyActionPayload>,
|
|
|
|
|
) => ({
|
|
|
|
|
...state,
|
|
|
|
|
isDirty: {
|
|
|
|
|
...state.isDirty,
|
|
|
|
|
[action.payload.id]: true,
|
|
|
|
|
},
|
|
|
|
|
}),
|
2019-12-11 15:14:38 +00:00
|
|
|
[ReduxActionTypes.UPDATE_ACTION_INIT]: (
|
|
|
|
|
state: ApiPaneReduxState,
|
2020-07-06 13:35:31 +00:00
|
|
|
action: ReduxAction<{ id: string }>,
|
2019-12-11 15:14:38 +00:00
|
|
|
) => ({
|
2019-11-13 07:34:59 +00:00
|
|
|
...state,
|
2019-12-11 15:14:38 +00:00
|
|
|
isSaving: {
|
|
|
|
|
...state.isSaving,
|
2020-07-06 13:35:31 +00:00
|
|
|
[action.payload.id]: true,
|
2019-12-11 15:14:38 +00:00
|
|
|
},
|
2019-11-13 07:34:59 +00:00
|
|
|
}),
|
2019-12-11 15:14:38 +00:00
|
|
|
[ReduxActionTypes.UPDATE_ACTION_SUCCESS]: (
|
|
|
|
|
state: ApiPaneReduxState,
|
2021-01-12 04:17:28 +00:00
|
|
|
action: ReduxAction<{ data: Action }>,
|
2019-12-11 15:14:38 +00:00
|
|
|
) => ({
|
2019-11-13 07:34:59 +00:00
|
|
|
...state,
|
2019-12-11 15:14:38 +00:00
|
|
|
isSaving: {
|
|
|
|
|
...state.isSaving,
|
|
|
|
|
[action.payload.data.id]: false,
|
|
|
|
|
},
|
2020-07-03 08:58:58 +00:00
|
|
|
isDirty: {
|
|
|
|
|
...state.isDirty,
|
|
|
|
|
[action.payload.data.id]: false,
|
|
|
|
|
},
|
2019-11-13 07:34:59 +00:00
|
|
|
}),
|
2019-12-11 15:14:38 +00:00
|
|
|
[ReduxActionErrorTypes.UPDATE_ACTION_ERROR]: (
|
|
|
|
|
state: ApiPaneReduxState,
|
|
|
|
|
action: ReduxAction<{ id: string }>,
|
|
|
|
|
) => ({
|
2019-11-13 07:34:59 +00:00
|
|
|
...state,
|
2019-12-11 15:14:38 +00:00
|
|
|
isSaving: {
|
|
|
|
|
...state.isSaving,
|
|
|
|
|
[action.payload.id]: false,
|
|
|
|
|
},
|
2019-11-13 07:34:59 +00:00
|
|
|
}),
|
2019-12-11 15:14:38 +00:00
|
|
|
[ReduxActionTypes.DELETE_ACTION_INIT]: (
|
|
|
|
|
state: ApiPaneReduxState,
|
|
|
|
|
action: ReduxAction<{ id: string }>,
|
|
|
|
|
) => ({
|
2019-11-13 07:34:59 +00:00
|
|
|
...state,
|
2019-12-11 15:14:38 +00:00
|
|
|
isDeleting: {
|
|
|
|
|
...state.isDeleting,
|
|
|
|
|
[action.payload.id]: true,
|
|
|
|
|
},
|
2019-11-13 07:34:59 +00:00
|
|
|
}),
|
2019-12-11 15:14:38 +00:00
|
|
|
[ReduxActionTypes.DELETE_ACTION_SUCCESS]: (
|
|
|
|
|
state: ApiPaneReduxState,
|
|
|
|
|
action: ReduxAction<{ id: string }>,
|
|
|
|
|
) => ({
|
2019-11-13 07:34:59 +00:00
|
|
|
...state,
|
2019-12-11 15:14:38 +00:00
|
|
|
isDeleting: {
|
|
|
|
|
...state.isDeleting,
|
|
|
|
|
[action.payload.id]: false,
|
|
|
|
|
},
|
2019-11-13 07:34:59 +00:00
|
|
|
}),
|
2019-12-11 15:14:38 +00:00
|
|
|
[ReduxActionErrorTypes.DELETE_ACTION_ERROR]: (
|
|
|
|
|
state: ApiPaneReduxState,
|
|
|
|
|
action: ReduxAction<{ id: string }>,
|
|
|
|
|
) => ({
|
2019-11-13 07:34:59 +00:00
|
|
|
...state,
|
2019-12-11 15:14:38 +00:00
|
|
|
isDeleting: {
|
|
|
|
|
...state.isDeleting,
|
|
|
|
|
[action.payload.id]: false,
|
|
|
|
|
},
|
2019-11-13 07:34:59 +00:00
|
|
|
}),
|
Feature/entity browse (#220)
# New Feature: Entity Explorer
- Entities are actions (apis and queries), datasources, pages, and widgets
- With this new feature, all entities in the application will be available
to view in the new entity explorer sidebar
- All existing application features from the api sidebar, query sidebar, datasource sidebar and pages sidebar
now are avialable on the entity explorer sidebar
- Users are now able to quickly switch to any entity in the application from the entity explorer sidebar.
- Users can also search all entities in the application from the new sidebar. Use cmd + f or ctrl + f to focus on the search input
- Users can rename entities from the new sidebar
- Users can also perform contextual actions on these entities like set a page as home page, copy/move actions, delete entity, etc from the context menu available alongside the entities in the sidebar
- Users can view the properties of the entities in the sidebar, as well as copy bindings to use in the application.
2020-08-10 08:52:45 +00:00
|
|
|
|
2020-04-28 10:47:59 +00:00
|
|
|
[ReduxActionTypes.SET_CURRENT_CATEGORY]: (
|
|
|
|
|
state: ApiPaneReduxState,
|
|
|
|
|
action: ReduxAction<{ category: string }>,
|
|
|
|
|
) => ({
|
|
|
|
|
...state,
|
|
|
|
|
currentCategory: action.payload.category,
|
|
|
|
|
}),
|
Feature/entity browse (#220)
# New Feature: Entity Explorer
- Entities are actions (apis and queries), datasources, pages, and widgets
- With this new feature, all entities in the application will be available
to view in the new entity explorer sidebar
- All existing application features from the api sidebar, query sidebar, datasource sidebar and pages sidebar
now are avialable on the entity explorer sidebar
- Users are now able to quickly switch to any entity in the application from the entity explorer sidebar.
- Users can also search all entities in the application from the new sidebar. Use cmd + f or ctrl + f to focus on the search input
- Users can rename entities from the new sidebar
- Users can also perform contextual actions on these entities like set a page as home page, copy/move actions, delete entity, etc from the context menu available alongside the entities in the sidebar
- Users can view the properties of the entities in the sidebar, as well as copy bindings to use in the application.
2020-08-10 08:52:45 +00:00
|
|
|
|
feat: Support body in GET API requests (#7127)
* WIP
* Refactoring HTTP Method & Content Type to be objects instead of arrays
TODO:
1. Set the default content-type for Get request to "None". Currently, it's raw
2. For None content-type, don't send the body field in the API request
* Almost working implementation for the None type
Currently, the body still gets sent in non-GET requests even if the None tab is selected.
* Adding object.freeze to prevent any modifications to HTTP_METHOD_ENUM
* WIP: Using enum & const for ts autocomplete
* working implementation for NONE type, apiContentType prop added to API actions
* WIP
* Refactoring HTTP Method & Content Type to be objects instead of arrays
TODO:
1. Set the default content-type for Get request to "None". Currently, it's raw
2. For None content-type, don't send the body field in the API request
* Almost working implementation for the None type
Currently, the body still gets sent in non-GET requests even if the None tab is selected.
* Adding object.freeze to prevent any modifications to HTTP_METHOD_ENUM
* WIP: Using enum & const for ts autocomplete
* working implementation for NONE type, apiContentType prop added to API actions
* adds apiContentType to actionConfiguration.formData object
* Handling apiContentType property in Rest API formData
* change apiContentType when user types content-type value and switches http method
* makes api editor as similar as possible to postman, project postman.
* Correcting the import in ApiEditorConstants
* Resolved all merge conflicts
* replay DSL functtionality
* removes unneccessary files from worker
* Fixes type declarations, naming e.t.c.
* fix server side merge conflicts
* fix client side merge conflicts
* fix failing cypress tests
Co-authored-by: Irongade <adeoluayangade@yahoo.com>
Co-authored-by: Ayangade Adeoluwa <37867493+Irongade@users.noreply.github.com>
2022-02-15 11:13:48 +00:00
|
|
|
/**
|
|
|
|
|
* This redux action sets the extraformData field for an action. This is used to select the
|
|
|
|
|
* appropriate body type tab selection in the Rest API plugin based on the content-type.
|
|
|
|
|
* This redux action can be extended to other functionalities as well in the future.
|
|
|
|
|
*
|
|
|
|
|
* @param {ApiPaneReduxState} state
|
|
|
|
|
* @param {ReduxAction} action
|
|
|
|
|
* @returns {ApiPaneReduxState}
|
|
|
|
|
*/
|
2020-05-07 07:56:37 +00:00
|
|
|
[ReduxActionTypes.SET_EXTRA_FORMDATA]: (
|
|
|
|
|
state: ApiPaneReduxState,
|
2020-11-03 13:05:40 +00:00
|
|
|
action: ReduxAction<{ id: string; values: Record<string, unknown> }>,
|
2020-05-07 07:56:37 +00:00
|
|
|
) => {
|
|
|
|
|
const { id, values } = action.payload;
|
|
|
|
|
return {
|
|
|
|
|
...state,
|
|
|
|
|
extraformData: {
|
|
|
|
|
...state.extraformData,
|
|
|
|
|
[id]: values,
|
|
|
|
|
},
|
|
|
|
|
};
|
|
|
|
|
},
|
2022-10-17 15:16:38 +00:00
|
|
|
[ReduxActionTypes.SET_API_PANE_CONFIG_SELECTED_TAB]: (
|
|
|
|
|
state: ApiPaneReduxState,
|
|
|
|
|
action: ReduxAction<{ selectedTabIndex: number }>,
|
|
|
|
|
) => {
|
|
|
|
|
const { selectedTabIndex } = action.payload;
|
|
|
|
|
return {
|
|
|
|
|
...state,
|
|
|
|
|
selectedConfigTabIndex: selectedTabIndex,
|
|
|
|
|
};
|
|
|
|
|
},
|
2022-11-25 03:47:00 +00:00
|
|
|
[ReduxActionTypes.SET_API_RIGHT_PANE_SELECTED_TAB]: (
|
|
|
|
|
state: ApiPaneReduxState,
|
|
|
|
|
action: ReduxAction<{ selectedTab: number }>,
|
|
|
|
|
) => {
|
|
|
|
|
const { selectedTab } = action.payload;
|
|
|
|
|
return {
|
|
|
|
|
...state,
|
|
|
|
|
selectedRightPaneTab: selectedTab,
|
|
|
|
|
};
|
|
|
|
|
},
|
2019-11-13 07:34:59 +00:00
|
|
|
});
|
|
|
|
|
|
|
|
|
|
export default apiPaneReducer;
|