PromucFlow_constructor/app/client/src/entities/FeatureFlags.ts

type FeatureFlags = {
  TEST_FLAG?: boolean;
  DATASOURCE_ENVIRONMENTS?: boolean;
  AUTO_LAYOUT?: boolean;
  ask_ai?: boolean;
  APP_NAVIGATION_LOGO_UPLOAD?: boolean;
};

export default FeatureFlags;
chore: Parallelise feature flags and user info API (#12263) 2022-04-07 17:57:32 +00:00			`type FeatureFlags = {`
chore: Clean up unused and completed feature flags (#23062) ## Description Clean up unused feature flags - LINTING - APP_TEMPLATE - JS_EDITOR - MULTIPLAYER - SNIPPET - TEMPLATES_PHASE_2 - RBAC - CONTEXT_SWITCHING - USAGE_AND_BILLING - DATASOURCE_ENVIRONMENTS #### Type of change - Chore (housekeeping or task changes that don't impact user perception) ## 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 - [ ] Manual - [ ] Jest - [ ] 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 - [ ] 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 - [ ] 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: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Test-plan-implementation#speedbreaker-features-to-consider-for-every-change) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans/_edit#areas-of-interest) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] 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 2023-05-25 05:28:41 +00:00			`TEST_FLAG?: boolean;`
chore: added type for feature flag (#18152) add: new type for env variable 2022-11-14 12:04:51 +00:00			`DATASOURCE_ENVIRONMENTS?: boolean;`
feat: Auto layout appsmith editor and mobile responsiveness (#21151) ## Description Core features of Auto Layout and mobile responsiveness, hidden under a feature flag. > Add a TL;DR when description is extra long (helps content team) 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 > Please delete options that are not relevant. - New feature (non-breaking change which adds functionality) ## How Has This Been Tested? > Manual regression and sanity tests for all fixed canvas functionality. - Manual - Jest - Cypress ## Checklist: ### Dev activity - [x] My code follows the style guidelines of this project - [x] 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 - [x] New and existing unit tests pass locally with my changes - [x] PR is being merged under a feature flag --------- Co-authored-by: Ashok Kumar M <35134347+marks0351@users.noreply.github.com> Co-authored-by: Arsalan <arsalanyaldram0211@outlook.com> Co-authored-by: Aswath K <aswath.sana@gmail.com> Co-authored-by: Aishwarya UR <aishwarya@appsmith.com> 2023-03-04 07:25:54 +00:00			`AUTO_LAYOUT?: boolean;`
fix: Renaming ff to conform to new type (#23050) We will now start to use lowercase for ff names. 2023-05-08 03:10:31 +00:00			`ask_ai?: boolean;`
fix: Hide logo upload behind a feature flag (#23596) ## Description With respect to some internal team conversations, we decided to hide the logo upload for app navigation behind a feature flag. If you're a team member, [follow this link to a Slack thread for details](https://theappsmith.slack.com/archives/C02JV8G1MP0/p1684387079809719). This PR makes the feature available to users with appsmith.com and moolya.com emails. #### PR fixes following issue(s) Fixes #23493 #### Type of change - Bug fix (non-breaking change which fixes an issue) - 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 - [ ] 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 - [ ] 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 - [ ] 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: - [x] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Test-plan-implementation#speedbreaker-features-to-consider-for-every-change) have been covered - [x] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans/_edit#areas-of-interest) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] 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 2023-05-24 11:58:55 +00:00			`APP_NAVIGATION_LOGO_UPLOAD?: boolean;`
chore: Parallelise feature flags and user info API (#12263) 2022-04-07 17:57:32 +00:00			`};`

			`export default FeatureFlags;`