PromucFlow_constructor/app/client/src/constants/QueryEditorConstants.ts
sneha122 0341de95b5
feat: For movies mock db, query should be populated with default values (#25403)
## Description

When we create movies mock DB, and create queries on top of it, then:
If datasource schema is available, then we need to populate the query
with defaults as shown below:
![Screenshot 2023-07-17 at 6 49 44
PM](https://github.com/appsmithorg/appsmith/assets/30018882/4fab934b-8900-4a9e-9660-5fe6e4ecc845)

When schema is not available, query would not be populated and shown in
blank state as below:
![Screenshot 2023-07-17 at 6 49 56
PM](https://github.com/appsmithorg/appsmith/assets/30018882/ae4635b3-19ef-497a-9383-f408c0234bf1)


#### PR fixes following issue(s)
Fixes #25320 
> if no issue exists, please create an issue and ask the maintainers
about this first
>
>
#### Media
> A video or a GIF is preferred. when using Loom, don’t embed because it
looks like it’s a GIF. instead, just link to the video
>
>
#### Type of change
- New feature (non-breaking change which adds functionality)
>
>
>
## Testing
>
#### How Has This Been Tested?
> Please describe the tests that you ran to verify your changes. Also
list any relevant details for your test configuration.
> Delete anything that is not relevant
- [x] Manual
- [ ] Jest
- [x] Cypress
>
>
#### 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
- [x] I have performed a self-review of my own code
- [x] 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
- [x] 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:
- [x] [Speedbreak
features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-)
have been covered
- [x] Test plan covers all impacted features and [areas of
interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-)
- [ ] Test plan has been peer reviewed by project stakeholders and other
QA members
- [x] Manually tested functionality on DP
- [ ] We had an implementation alignment call with stakeholders post QA
Round 2
- [ ] Cypress test cases have been added and approved by SDET/manual QA
- [ ] Added `Test Plan Approved` label after Cypress tests were reviewed
- [ ] Added `Test Plan Approved` label after JUnit tests were reviewed

---------

Co-authored-by: “sneha122” <“sneha@appsmith.com”>
Co-authored-by: Aishwarya UR <aishwarya@appsmith.com>
2023-07-24 17:32:50 +05:30

32 lines
642 B
TypeScript

import { PluginPackageName, PluginName } from "entities/Action";
export const QUERY_BODY_FIELDS = [
"actionConfiguration.body",
"actionConfiguration.formData.body.data",
];
export const SQL_DATASOURCES: Array<string> = [
PluginName.POSTGRES,
PluginName.MS_SQL,
PluginName.MY_SQL,
PluginName.ORACLE,
PluginName.SNOWFLAKE,
PluginName.ARANGODB,
PluginName.REDSHIFT,
];
export const PLUGIN_PACKAGE_DBS = [
PluginPackageName.POSTGRES,
PluginPackageName.MONGO,
];
export const MOCK_DB_TABLE_NAMES = {
MOVIES: "movies",
USERS: "public.users",
};
export enum EDITOR_TABS {
QUERY = "QUERY",
SETTINGS = "SETTINGS",
}