Protei/PromucFlow_constructor
2
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity
087a1b1fac
PromucFlow_constructor/app/client/src/entities/FeatureFlags.ts

19 lines
438 B
TypeScript
Raw Normal View History

chore: Parallelise feature flags and user info API (#12263)
2022-04-07 17:57:32 +00:00
type FeatureFlags = {
APP_TEMPLATE?: boolean;
JS_EDITOR?: boolean;
MULTIPLAYER?: boolean;
SNIPPET?: boolean;
chore: hide templates v2 behind feature flag (#17034)
2022-10-10 07:44:37 +00:00
TEMPLATES_PHASE_2?: boolean;
fix: Rest of the audit logs potential auto-merge errors. (#17192) * fix: EE-CE parity due to audit-logs * fix: rest of the audit-logs potential failures * fix: future conflict with RBAC
2022-10-04 11:18:35 +00:00
RBAC?: boolean;
feat: Maintain Focus and Context Phase 1 (#16317)
2022-10-17 15:16:38 +00:00
CONTEXT_SWITCHING?: boolean;
chore: code split usage and billing files (#19436) ## Description Since Usage & Billing is EE only, there are a few components which needs to be code splitted. So code splitted those files and also added feature flag for Usage & Billing. TL;DR Code split usage and billing files Fixes [#146](https://github.com/appsmithorg/cloud-services/issues/146) ## Type of change > Please delete options that are not relevant. - Code splitting ## How Has This Been Tested? - Manual ## 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 - [ ] 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
2023-01-10 05:39:15 +00:00
USAGE_AND_BILLING?: 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: Multi Pane IDE: Phase 1 (#19261) ## Description Starts work on the Multi Pane IDE that would be behind a feature flag right now. We will continue work on this behind the scenes > New shiny Multi Pane layout that will be unwrapped after a few months Fixes #19210 ## Type of change - New feature (non-breaking change which adds functionality) - Breaking change (fix or feature that would cause existing functionality to not work as expected) ## How Has This Been Tested? > Please describe the tests that you ran to verify your changes. Provide instructions, so we can reproduce. > Please also list any relevant details for your test configuration. > Delete anything that is not important - 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: - [ ] 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
2023-01-09 05:24:41 +00:00
MULTIPLE_PANES?: 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;
chore: Render below the fold widget components when browser is idle using Intersection Observer (#18747) ## Description In order to improve the first load of the applications, now we're only rendering the widget components that are [above the fold](https://en.wikipedia.org/wiki/Above_the_fold#In_web_design) right away and rendering the other widget components whenever the browser is idle. This decreases the amount of time it takes before the first paint on the screen. This is getting shipped behind a feature flag!
2023-02-08 11:23:39 +00:00
LAZY_CANVAS_RENDERING?: boolean;
chore: Add ONE_CLICK_BINDING feature flag for the one click binding e… (#21569) ## Description - Add a feature flag to hide all the one-click binding changes until properly integrated. Fixes #21503 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. - Bug fix (non-breaking change which fixes an issue) - New feature (non-breaking change which adds functionality) - Breaking change (fix or feature that would cause existing functionality to not work as expected) - Chore (housekeeping or task changes that don't impact user perception) - This change requires a documentation update ## How Has This Been Tested? > Please describe the tests that you ran to verify your changes. Provide instructions, so we can reproduce. > Please also list any relevant details for your test configuration. > Delete anything that is not important - 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 - [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 ### 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
2023-03-21 05:03:50 +00:00
ONE_CLICK_BINDING?: boolean;
chore: code splitting changes for appsmith ai v0.1 (#22521) ## Description This PR only contains interfaces for the EE AI feat. These are temporary changes ## Type of change - Chore (housekeeping or task changes that don't impact user perception) ## How Has This Been Tested? - Manual ### 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 - [x] New and existing unit tests pass locally with my changes - [x] My changes generate no new warnings - [ ] I have made corresponding changes to the documentation - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] 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
2023-04-20 15:12:35 +00:00
CHAT_AI?: boolean;
chore: Parallelise feature flags and user info API (#12263)
2022-04-07 17:57:32 +00:00
};
export default FeatureFlags;
Reference in New Issue Copy Permalink