PromucFlow_constructor/app/client/src/components/propertyControls/StyledControls.tsx

450 lines
11 KiB
TypeScript
Raw Normal View History

import React, { RefObject, useEffect, useRef } from "react";
chore: update Styled components to latest version and related cleanup (#19284) ## Description We need to upgrade `styled-components`, so that it will become easy to upgrade to version 6.0 when it is out. This is because, v6.0 has an important functionality which isn't available in today's version. ### Tasks completed - Update Styled components to latest version. - Prepare codebase by cleaning up the styled components functions that will be deprecated in version 6 - We are still using the `withTheme` HOC, we should instead use the `useTheme` hook (best practices) - Remove the `AnyStyledComponent` type it is un-necessary and will be deprecated Fixes #19463 ## Type of change - Non breaking change. The application should work as before and should not effect any visual elements or UI. ## How Has This Been Tested? - Manual @appsmithorg/qa please refer to the test plan for areas of interest. - Cypress: All existing test cases must pass. ### Test Plan - We need to do a sanity check on the Product Updates Modal, Release section. - We also need to do a sanity check on the Login, Signup, ResetPassword pages. - I think we can merge this Pull Request and continue with our weekly regression, because there are no style changes in this Pull Request, everything should work as expected. ## 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-13 11:05:59 +00:00
import styled, { css } from "styled-components";
import { Classes, MenuItem, Menu } from "@blueprintjs/core";
2019-11-25 05:07:27 +00:00
import { ContainerOrientation } from "constants/WidgetConstants";
import { DateRangeInput } from "@blueprintjs/datetime";
2020-02-18 10:41:52 +00:00
import { Colors } from "constants/Colors";
chore: update Styled components to latest version and related cleanup (#19284) ## Description We need to upgrade `styled-components`, so that it will become easy to upgrade to version 6.0 when it is out. This is because, v6.0 has an important functionality which isn't available in today's version. ### Tasks completed - Update Styled components to latest version. - Prepare codebase by cleaning up the styled components functions that will be deprecated in version 6 - We are still using the `withTheme` HOC, we should instead use the `useTheme` hook (best practices) - Remove the `AnyStyledComponent` type it is un-necessary and will be deprecated Fixes #19463 ## Type of change - Non breaking change. The application should work as before and should not effect any visual elements or UI. ## How Has This Been Tested? - Manual @appsmithorg/qa please refer to the test plan for areas of interest. - Cypress: All existing test cases must pass. ### Test Plan - We need to do a sanity check on the Product Updates Modal, Release section. - We also need to do a sanity check on the Login, Signup, ResetPassword pages. - I think we can merge this Pull Request and continue with our weekly regression, because there are no style changes in this Pull Request, everything should work as expected. ## 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-13 11:05:59 +00:00
import { Skin } from "constants/DefaultTheme";
import { ControlIcons } from "icons/ControlIcons";
import { FormIcons } from "icons/FormIcons";
feat: Migrate design system components import to design-system repo - I (#15562) * Icon component deleted and changed the imports in refrence places * design system package version changed * import changes * Delete TextInput.tsx * Change imports * Change single named import * Update package * Update package * Delete ScrollIndicator.tsx * Change imports * Icon import completed * Event type added * Changed Button component imports * import change button * Button onclick type fix * Label with Tooltip import changes * Changed breadcrumbs import * EmojiPicker and Emoji Reaction import changes * AppIcon import change * import bug fix * Menu Item import chnages * Icon selector imports changed * Delete LabelWithTooltip.tsx * Change imports across the app * Update package version * Update version number for design-system * Delete Checkbox.tsx * Remove the exports * Add lock file for ds package update * Change imports * default import -> named * Update release version * Make arg type explicit * Updated design-system to latest release * Missing file mysteriously comes back and is updated accordingly * changes design-system package version * Add types to arguments in the onChange for text input * onBlur type fix * Search component in property pane * WDS button changes reverted * package version bumped * conflict fix * Remove Dropdown, change imports * Category import fix * fix: table icon size import * Bump version of design system package * Yarn lock Co-authored-by: Tanvi Bhakta <tanvibhakta@gmail.com>
2022-08-22 05:09:39 +00:00
import {
Button,
Dropdown,
InputWrapper,
TextInput,
TextInputProps,
feat: Renamed design system package (#19854) ## Description This PR includes changes for renaming design system package. Since we are building new package for the refactored design system components, the old package is renaming to design-system-old. Fixes #19536 ## 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? - 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 - [ ] 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-23 03:50:47 +00:00
} from "design-system-old";
import { IconWrapper } from "constants/IconConstants";
import useInteractionAnalyticsEvent from "utils/hooks/useInteractionAnalyticsEvent";
feat: Renamed design system package (#19854) ## Description This PR includes changes for renaming design system package. Since we are building new package for the refactored design system components, the old package is renaming to design-system-old. Fixes #19536 ## 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? - 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 - [ ] 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-23 03:50:47 +00:00
import { Checkbox } from "design-system-old";
2019-11-05 05:09:50 +00:00
type ControlWrapperProps = {
orientation?: ContainerOrientation;
isAction?: boolean;
2019-11-05 05:09:50 +00:00
};
export const ControlWrapper = styled.div<ControlWrapperProps>`
2020-12-24 04:32:25 +00:00
display: ${(props) =>
props.orientation === "HORIZONTAL" ? "flex" : "block"};
2019-11-07 10:33:04 +00:00
justify-content: space-between;
align-items: center;
2020-12-24 04:32:25 +00:00
flex-direction: ${(props) =>
2020-06-10 13:41:26 +00:00
props.orientation === "VERTICAL" ? "column" : "row"};
padding-top: 4px;
&:not(:last-of-type) {
padding-bottom: 4px;
}
& > label {
color: ${(props) => props.theme.colors.propertyPane.label};
2020-12-24 04:32:25 +00:00
margin-bottom: ${(props) => props.theme.spaces[1]}px;
font-size: ${(props) => props.theme.fontSizes[3]}px;
}
&&& > label:first-of-type {
display: block;
}
&&& > label {
display: inline-block;
2020-06-10 13:41:26 +00:00
}
feat: App Theming (#9714) * fix style bugs * fix select styles * test: fix font size issue for cypress tests * incorporate ashit feedback * test: addresed review comments for cypress tests * add analytics events * height issue in view mode * incorporate code review feedbacks * incorporate code review feedbacks * refactor: addressed review comments; removed border radius and box shadow for text widget; Updated migrations * feat: Makes shadow and radius controls keyboard accessible (#11547) * makes shadow and radius controls keyboard accessible * removes unused imports * moves options out of render method * fix: changed the misnomer background property name to the relevant property name * fix: border radius issue for the map widget * address qa bugs * address qa bugs * fix ux of theming pane when widget is selected * fix: * added backgroundColor to the video widget * restricted pop-over border radius to 0.375rem * added box shadow for the input group for select widget * fix: added delete icon in the delete theme modal * address qa bugs * change checkbox column size in config * add js convertible to button color * remove unused imports * test: fixed jest tests * fix primary color typo * fix: migrations for the theming * fix: * Removed background color from MultiTreeSelect and TreeSelect component. * grouped button's menu button pop over border radius restricting to 0.375rem. * test: updated Dsl migration UT * address qa bugs * address qa bugs * fix: address qa comments * address qa bugs * fix: * migration issue; * unit test cases; * fix rating widget scroll issue * fix youtube video border radius bug * fix select widget * fix select widgets styles * address qa bugs * merge conflicts * makes the reset button keyboard accessible (#12134) * -resolved merge conflicts * address qa bugs * fix: labelTextSize migration fixes * refactor: * made changes to the fontSizeUtils function * fixed the issue related to unit tests * fix button group widget * remove unused imports * fix: fixed the text size migration for the table widget * refactor: addressed review comments for the table widget theming migration * fix button group widget * add init calls for view mode * json form init theme changes * fix: added migration for boxShadow, borderRadius and textSizes for table widget * fix broken fields * test: fixed unit tests * wip * inconsistancy fixes and schemaItem update in updateHook/fieldConfiguration * feat: init json form migration theming * json form primaryColor -> accentColor * update table widget * update table widget * object field label styling * fix: migration related to the JSON form * fix: fixed labelTextSize migration for JSON form nested widgets * property control nested stylesheet lookup * JSONForm label styles form array items * show label for checkbox field array item * fix button group widget * wip * refactor: addressed table widget review comments * refactor: addressed ashit review comments; * added childStylesheet for widgets * feat: Keyboard navigable Color Picker control (#11797) * Makes ColorPicker keyboard accessible * seperate out keyboard and mouse interactions * fix issue with not focusing back to input * Adds test for Color picker * chore: added comment for the boxShadow property * fix: * added unit test cases for the widget and property utils * resolved warning messages * wip * theme config update * fix merge conflicts * refactor: moved theming migration inside the migrations folder * fix qa bugs * fix jest test * fix: unit test cases * fix table column creation logic * refactor: addressed review comments for migrations * fix: Overriding margin and padding for custom render in the dropdown component (#12875) * * fix for custom render padding and margin in ADS dropdown * * fix for removing padding from normal render options * refactor: moved the boxShadow condition to the variable * fix qa bugs * fix: migration QA callouts for audio recorder widget * refactor: added updated comments for boxShadow migration for table widget * fix theme binfings for JSONForm fields under Object * fix table widget theming bug * fix: addressed code review comments * fix: unit test cases * fix: qa migration callouts * fix table widget theming bug * fix JSONForm currency input dropdown not submit form * Added new tests - AppThemingSpec * fix qa bugs * fix unit test * fix JSONForm cellBorderWidth to have default value post migration * fix unit test * fix qa bugs * remove unused imports * fix qa bugs * fix JSONForm input height issue * fix qa bugs * Updating Theming spec * * dropdown color fixes (#13249) * fix caching issue ; * Fixed Theming tests * fix tests * fix tab widget tests * fix: json form children level migration issue * fix table widget tests * Updated test * updated tests * updated test * updated tests * updated tests * updated pageload * fix cypress tests * remove cypress created files * fix color picker issues * Failure fixes * Fixed some more tests * fix: cypress test failures * fix tests * remove consoles * fix table tests * fix qa bugs * updating snapshots for AppPageLayout_spec as per new UI * fix rating widget bug * fix qa bugs * fix: * cypress failing tests * Migration QA callouts * Removed unused imports * update constract check algo * fix color contrast issue * fix: cypress failure test cases * update font sizes labels * fix regression bugs * fix: * JSON form labelTextSize issue fix * Updated comment for the fontSizeUtility function * migrations issues related to table widget borderRadius and boxShadow * fix: default labelTextSize issue for the Input and Select families * fix regression bugs * fix regression bugs * PassingParams spec - added wait time * fix: font family default value issue on JS toggle * fix js toggle issue in text widget * fix tests * fix tests * fix tests * fix cypress tests * fix regression bugs * fix regression bugs * fix: * refactored table widget migration function as per review comments, * added default value to the widget * fix: failing unit test cases * fix theming spec * fix cypress tests * test: fixed failed cypress test * incorporate ashit feedback * fix cypress tests * fix: addressed review comments * comment out table cypress test * fix merge conflicts * comment out color picker tests Co-authored-by: Pawan Kumar <pawankumar@Pawans-MacBook-Pro.local> Co-authored-by: keyurparalkar <keyur@appsmith.com> Co-authored-by: Aswath K <aswath@appsmith.com> Co-authored-by: Nayan <nayan@appsmith.com> Co-authored-by: Ashit Rath <ashit@appsmith.com> Co-authored-by: balajisoundar <balaji@appsmith.com> Co-authored-by: albinAppsmith <87797149+albinAppsmith@users.noreply.github.com> Co-authored-by: Aishwarya UR <aishwarya@appsmith.com> Co-authored-by: apple <nandan@thinkify.io> Co-authored-by: Parthvi Goswami <parthvigoswami@Parthvis-MacBook-Pro.local>
2022-05-04 09:45:57 +00:00
&:focus-within .reset-button {
display: block;
}
`;
export const ControlPropertyLabelContainer = styled.div`
display: flex;
align-items: center;
2020-03-20 09:45:44 +00:00
label {
color: ${Colors.GRAY_700};
2020-12-24 04:32:25 +00:00
margin-bottom: ${(props) => props.theme.spaces[1]}px;
font-size: ${(props) => props.theme.fontSizes[3]}px;
}
2020-03-20 09:45:44 +00:00
.underline {
2020-12-24 04:32:25 +00:00
color: ${(props) => props.theme.colors.paneTextUnderline};
2020-03-20 09:45:44 +00:00
}
`;
export const JSToggleButton = styled.button<{ active: boolean }>`
margin: 4px;
margin-top: 0px;
& ${IconWrapper} {
cursor: ${(props) => (props.disabled ? "not-allowed" : "pointer")};
}
height: auto;
width: 28px;
height: 16px;
border: 0.5px solid
${(props) => (props.disabled ? Colors.GRAY_400 : Colors.GRAY_700)};
background-color: ${(props) =>
props.active
? props.disabled
? Colors.GRAY_400
: Colors.GRAY_800
: props.disabled
? Colors.GRAY_200
: Colors.WHITE};
&:hover {
background-color: ${(props) =>
props.disabled
? props.active
? Colors.GRAY_400
: Colors.GRAY_200
: props.active
? Colors.GRAY_900
: Colors.GRAY_200};
}
& > div {
display: flex;
align-items: center;
justify-content: center;
feat: Property pane dropdown overflow issues (#8236) * * hide subtext for date picker fix * EE clicking on entity, unfolding/folding added * * bug fixes in action dropdown * bug fix for cursor * fix: 8190 background api request and welcome helper button (#8281) * chore: Move action/js debugger tabs related logic to a common component (#8199) * removed background of api request textbox and added hover text on "no thanks" button Co-authored-by: akash-codemonk <67054171+akash-codemonk@users.noreply.github.com> * fix: added scrolling in invited users more popup (#8226) * added scrolling in invited users more popup * always scrollbar displaying on invited users pan * fixed issue related with 8190 * updated cursor of invited users more * replace edit data source icon with remix icon (#8192) * * active text color * fix: dropdownlist props issue (#8322) * Commented failing JS tests (#8276) Co-authored-by: Yatin Chaubal <yatin.chaubal@gmail.com> * docs: Update ServerSetup.md (#8255) * Make port customizable from env variable (#8288) * fix: issue with string templates (#7848) * Remove bracket highlight on error * fix string template issue * using string template to join strings * fix breaking tests * fixed props pass issue Co-authored-by: yatinappsmith <84702014+yatinappsmith@users.noreply.github.com> Co-authored-by: Yatin Chaubal <yatin.chaubal@gmail.com> Co-authored-by: Abhishek Choudhary <shreemaan.abhishek@gmail.com> Co-authored-by: Shrikant Sharat Kandula <shrikant@appsmith.com> Co-authored-by: Vinod <4994565+vnodecg@users.noreply.github.com> * * bug fixes * * bug fix * * test cases fix * - test case fix * * test fixes * * bug fix in test case Co-authored-by: haojin111 <63215848+haojin111@users.noreply.github.com> Co-authored-by: akash-codemonk <67054171+akash-codemonk@users.noreply.github.com> Co-authored-by: yatinappsmith <84702014+yatinappsmith@users.noreply.github.com> Co-authored-by: Yatin Chaubal <yatin.chaubal@gmail.com> Co-authored-by: Abhishek Choudhary <shreemaan.abhishek@gmail.com> Co-authored-by: Shrikant Sharat Kandula <shrikant@appsmith.com> Co-authored-by: Vinod <4994565+vnodecg@users.noreply.github.com> Co-authored-by: Arpit Mohan <arpit@appsmith.com>
2021-10-11 06:01:05 +00:00
cursor: pointer;
}
&&& svg {
width: 28px;
height: 16px;
transform: scale(1.4);
rect {
fill: transparent;
}
path {
fill: ${(props) => (props.active ? Colors.WHITE : Colors.GRAY_700)};
}
}
`;
2020-02-18 10:41:52 +00:00
export const StyledDropDownContainer = styled.div`
width: 100%;
height: 100%;
`;
export const StyledDropDown = styled(Dropdown)`
background-color: ${(props) => props.theme.colors.propertyPane.buttonText};
box-shadow: none;
/*
We use this font family to show emoji flags
on windows devices
*/
.left-icon-wrapper {
font-family: "Twemoji Country Flags";
}
2020-02-18 10:41:52 +00:00
`;
2020-05-22 05:15:41 +00:00
export const StyledMenu = styled(Menu)`
&& {
background: ${(props) => props.theme.dropdown[Skin.LIGHT].background};
border-radius: unset;
2020-05-22 05:15:41 +00:00
}
.bp3-submenu .bp3-menu {
background: ${(props) => props.theme.dropdown[Skin.LIGHT].background};
2020-05-22 05:15:41 +00:00
}
`;
2020-02-20 15:03:14 +00:00
export const StyledMenuItem = styled(MenuItem)`
&&&&&& {
border-radius: 0;
background: ${(props) => props.theme.dropdown[Skin.LIGHT].background};
color: ${(props) => props.theme.dropdown[Skin.LIGHT].inActiveText};
2020-05-22 05:15:41 +00:00
padding: 4px 8px;
margin: 4px 0px;
2020-02-20 15:03:14 +00:00
&:hover {
background: ${(props) => props.theme.dropdown[Skin.LIGHT].hoverBG};
2020-04-22 09:15:24 +00:00
&&&.bp3-menu-item.bp3-intent-danger:hover {
color: ${(props) => props.theme.colors.error};
2020-04-22 09:15:24 +00:00
}
2020-02-20 15:03:14 +00:00
}
&.${Classes.ACTIVE} {
background: ${(props) => props.theme.dropdown[Skin.LIGHT].hoverBG};
2020-02-20 15:03:14 +00:00
position: relative;
&.single-select {
&:before {
left: 0;
top: -2px;
position: absolute;
content: "";
background: ${(props) => props.theme.dropdown[Skin.LIGHT].hoverBG};
border-radius: 0;
2020-02-20 15:03:14 +00:00
width: 4px;
height: 100%;
}
}
}
2020-05-22 05:15:41 +00:00
&&&& .${Classes.MENU} {
background: ${(props) => props.theme.dropdown[Skin.LIGHT].inActiveBG};
2020-05-22 05:15:41 +00:00
}
2020-02-20 15:03:14 +00:00
}
`;
2019-12-06 13:16:08 +00:00
export const StyledDynamicInput = styled.div`
2020-04-15 11:42:11 +00:00
width: 100%;
2019-12-06 13:16:08 +00:00
&&& {
input {
border: none;
2020-12-24 04:32:25 +00:00
color: ${(props) => props.theme.colors.textOnDarkBG};
background: ${(props) => props.theme.colors.paneInputBG};
2019-12-06 13:16:08 +00:00
&:focus {
border: none;
2020-12-24 04:32:25 +00:00
color: ${(props) => props.theme.colors.textOnDarkBG};
background: ${(props) => props.theme.colors.paneInputBG};
2019-12-06 13:16:08 +00:00
}
}
}
`;
const InputGroup = styled(TextInput)`
width: 100%;
border-radius: 0;
background-color: ${(props) => props.theme.colors.propertyPane.radioGroupBg};
color: ${(props) => props.theme.colors.propertyPane.radioGroupText};
&:focus {
box-shadow: none;
2020-03-20 11:03:50 +00:00
}
2019-11-07 10:33:04 +00:00
`;
const StyledInputWrapper = styled.div`
width: 100%;
&:focus ${InputWrapper} {
border: 1px solid var(--appsmith-input-focus-border-color);
}
`;
export const StyledInputGroup = React.forwardRef(
(props: TextInputProps, ref) => {
let inputRef = useRef<HTMLInputElement>(null);
const wrapperRef = useRef<HTMLInputElement>(null);
const { dispatchInteractionAnalyticsEvent } = useInteractionAnalyticsEvent<
HTMLInputElement
>(false, wrapperRef);
if (ref) inputRef = ref as RefObject<HTMLInputElement>;
useEffect(() => {
window.addEventListener("keydown", handleKeydown);
return () => {
window.removeEventListener("keydown", handleKeydown);
};
}, []);
const handleKeydown = (e: KeyboardEvent) => {
switch (e.key) {
case "Enter":
case " ":
if (document.activeElement === wrapperRef?.current) {
dispatchInteractionAnalyticsEvent({ key: e.key });
inputRef?.current?.focus();
e.preventDefault();
}
break;
case "Escape":
if (document.activeElement === inputRef?.current) {
dispatchInteractionAnalyticsEvent({ key: e.key });
wrapperRef?.current?.focus();
e.preventDefault();
}
break;
case "Tab":
if (document.activeElement === wrapperRef?.current) {
dispatchInteractionAnalyticsEvent({
key: `${e.shiftKey ? "Shift+" : ""}${e.key}`,
});
}
break;
}
};
return (
<StyledInputWrapper ref={wrapperRef} tabIndex={0}>
<InputGroup ref={inputRef} {...props} tabIndex={-1} width="auto" />
</StyledInputWrapper>
);
},
);
StyledInputGroup.displayName = "StyledInputGroup";
export const StyledDateRangePicker = styled(DateRangeInput)`
> input {
2020-12-24 04:32:25 +00:00
color: ${(props) => props.theme.colors.textOnDarkBG};
background: ${(props) => props.theme.colors.paneInputBG};
border: 1px solid green;
}
`;
2020-05-22 05:15:41 +00:00
export const FieldWrapper = styled.div`
position: relative;
width: 100%;
`;
chore: update Styled components to latest version and related cleanup (#19284) ## Description We need to upgrade `styled-components`, so that it will become easy to upgrade to version 6.0 when it is out. This is because, v6.0 has an important functionality which isn't available in today's version. ### Tasks completed - Update Styled components to latest version. - Prepare codebase by cleaning up the styled components functions that will be deprecated in version 6 - We are still using the `withTheme` HOC, we should instead use the `useTheme` hook (best practices) - Remove the `AnyStyledComponent` type it is un-necessary and will be deprecated Fixes #19463 ## Type of change - Non breaking change. The application should work as before and should not effect any visual elements or UI. ## How Has This Been Tested? - Manual @appsmithorg/qa please refer to the test plan for areas of interest. - Cypress: All existing test cases must pass. ### Test Plan - We need to do a sanity check on the Product Updates Modal, Release section. - We also need to do a sanity check on the Login, Signup, ResetPassword pages. - I think we can merge this Pull Request and continue with our weekly regression, because there are no style changes in this Pull Request, everything should work as expected. ## 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-13 11:05:59 +00:00
export const StyledDragIcon = styled(ControlIcons.DRAG_CONTROL)`
padding: 0;
position: absolute;
margin-right: 15px;
cursor: move;
z-index: 1;
left: 4px;
&& svg {
width: 16px;
height: 16px;
position: relative;
top: 2px;
path {
fill: ${(props) => props.theme.colors.propertyPane.iconColor};
}
}
`;
feat: added column freeze and unfreeze functionality to table widget (#18757) **PRD**: https://www.notion.so/appsmith/Ability-to-freeze-columns-dd118f7ed2e14e008ee305056b79874a?d=300f4968889244da9f737e1bfd8c06dc#2ddaf28e10a0475cb69f1af77b938d0b This PR adds the following features to the table widget: - Freeze the columns to the left or right of the table.(Both canvas and page view mode). - Unfreeze the frozen columns. (Both canvas and page view mode). - Columns that are left frozen, will get unfrozen at a position after the last left frozen column. (Both canvas and page view mode). - Columns that are right frozen, will get unfrozen at a position before the first right frozen column. (Both canvas and page view mode). - Column order can be persisted in the Page view mode. - Users can also unfreeze the columns that are frozen by the developers. - Columns that are frozen cannot be reordered(Both canvas and page view mode) - **Property pane changes (Columns property)**: - If the column is frozen to the left then that column should appear at top of the list. - If the column is frozen to the right then that column should appear at the bottom of the list. - The columns that are frozen cannot be moved or re-ordered in the list. They remain fixed in their position. - In-Page mode, If there is a change in frozen or unfrozen columns in multiple tables then the order of columns and frozen and unfrozen columns should get persisted on refresh i.e. changes should get persisted across refreshes.
2023-02-15 11:42:46 +00:00
export const StyledPinIcon = styled(ControlIcons.PIN)`
padding: 0;
position: absolute;
margin-right: 15px;
cursor: default;
z-index: 1;
left: 4px;
&& svg {
width: 16px;
height: 16px;
position: relative;
top: 2px;
path {
fill: ${(props) => props.theme.colors.propertyPane.iconColor};
}
}
`;
export const FlexWrapper = styled.div`
display: flex;
`;
export const StyledPropertyPaneButton = styled(Button)`
margin-top: 4px;
margin-left: auto;
display: flex;
justify-content: flex-end;
&&& svg {
width: 14px;
height: 14px;
path {
fill: ${Colors.GREY_8};
stroke: ${Colors.GREY_8};
}
}
`;
export const StyledOptionControlInputGroup = styled(StyledInputGroup)<{
rightPadding: number;
}>`
width: 100%;
padding-left: 20px;
padding-right: ${(props) => props.rightPadding}px;
padding-bottom: 4px;
text-overflow: ellipsis;
background: inherit;
&&& {
input {
padding-left: 24px;
border: none;
color: ${(props) => props.theme.colors.textOnDarkBG};
&:focus {
border: none;
color: ${(props) => props.theme.colors.textOnDarkBG};
}
}
}
`;
/* Used in Draggable List Card component in Property pane */
export const StyledActionContainer = styled.div`
position: absolute;
right: 0px;
display: flex;
`;
const CommonIconStyles = css`
padding: 0;
margin-right: 10px;
cursor: pointer;
display: flex;
align-items: center;
`;
chore: update Styled components to latest version and related cleanup (#19284) ## Description We need to upgrade `styled-components`, so that it will become easy to upgrade to version 6.0 when it is out. This is because, v6.0 has an important functionality which isn't available in today's version. ### Tasks completed - Update Styled components to latest version. - Prepare codebase by cleaning up the styled components functions that will be deprecated in version 6 - We are still using the `withTheme` HOC, we should instead use the `useTheme` hook (best practices) - Remove the `AnyStyledComponent` type it is un-necessary and will be deprecated Fixes #19463 ## Type of change - Non breaking change. The application should work as before and should not effect any visual elements or UI. ## How Has This Been Tested? - Manual @appsmithorg/qa please refer to the test plan for areas of interest. - Cypress: All existing test cases must pass. ### Test Plan - We need to do a sanity check on the Product Updates Modal, Release section. - We also need to do a sanity check on the Login, Signup, ResetPassword pages. - I think we can merge this Pull Request and continue with our weekly regression, because there are no style changes in this Pull Request, everything should work as expected. ## 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-13 11:05:59 +00:00
export const StyledEditIcon = styled(ControlIcons.SETTINGS_CONTROL)`
${CommonIconStyles}
&& svg {
width: 16px;
height: 16px;
position: relative;
path {
fill: ${(props) => props.theme.colors.propertyPane.iconColor};
}
}
`;
chore: update Styled components to latest version and related cleanup (#19284) ## Description We need to upgrade `styled-components`, so that it will become easy to upgrade to version 6.0 when it is out. This is because, v6.0 has an important functionality which isn't available in today's version. ### Tasks completed - Update Styled components to latest version. - Prepare codebase by cleaning up the styled components functions that will be deprecated in version 6 - We are still using the `withTheme` HOC, we should instead use the `useTheme` hook (best practices) - Remove the `AnyStyledComponent` type it is un-necessary and will be deprecated Fixes #19463 ## Type of change - Non breaking change. The application should work as before and should not effect any visual elements or UI. ## How Has This Been Tested? - Manual @appsmithorg/qa please refer to the test plan for areas of interest. - Cypress: All existing test cases must pass. ### Test Plan - We need to do a sanity check on the Product Updates Modal, Release section. - We also need to do a sanity check on the Login, Signup, ResetPassword pages. - I think we can merge this Pull Request and continue with our weekly regression, because there are no style changes in this Pull Request, everything should work as expected. ## 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-13 11:05:59 +00:00
export const StyledVisibleIcon = styled(ControlIcons.SHOW_COLUMN)`
${CommonIconStyles}
&& svg {
width: 16px;
height: 16px;
position: relative;
path {
fill: ${(props) => props.theme.colors.propertyPane.iconColor};
}
}
`;
chore: update Styled components to latest version and related cleanup (#19284) ## Description We need to upgrade `styled-components`, so that it will become easy to upgrade to version 6.0 when it is out. This is because, v6.0 has an important functionality which isn't available in today's version. ### Tasks completed - Update Styled components to latest version. - Prepare codebase by cleaning up the styled components functions that will be deprecated in version 6 - We are still using the `withTheme` HOC, we should instead use the `useTheme` hook (best practices) - Remove the `AnyStyledComponent` type it is un-necessary and will be deprecated Fixes #19463 ## Type of change - Non breaking change. The application should work as before and should not effect any visual elements or UI. ## How Has This Been Tested? - Manual @appsmithorg/qa please refer to the test plan for areas of interest. - Cypress: All existing test cases must pass. ### Test Plan - We need to do a sanity check on the Product Updates Modal, Release section. - We also need to do a sanity check on the Login, Signup, ResetPassword pages. - I think we can merge this Pull Request and continue with our weekly regression, because there are no style changes in this Pull Request, everything should work as expected. ## 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-13 11:05:59 +00:00
export const StyledHiddenIcon = styled(ControlIcons.HIDE_COLUMN)`
${CommonIconStyles}
&& svg {
width: 16px;
height: 16px;
position: relative;
path {
fill: ${(props) => props.theme.colors.propertyPane.iconColor};
}
}
`;
chore: update Styled components to latest version and related cleanup (#19284) ## Description We need to upgrade `styled-components`, so that it will become easy to upgrade to version 6.0 when it is out. This is because, v6.0 has an important functionality which isn't available in today's version. ### Tasks completed - Update Styled components to latest version. - Prepare codebase by cleaning up the styled components functions that will be deprecated in version 6 - We are still using the `withTheme` HOC, we should instead use the `useTheme` hook (best practices) - Remove the `AnyStyledComponent` type it is un-necessary and will be deprecated Fixes #19463 ## Type of change - Non breaking change. The application should work as before and should not effect any visual elements or UI. ## How Has This Been Tested? - Manual @appsmithorg/qa please refer to the test plan for areas of interest. - Cypress: All existing test cases must pass. ### Test Plan - We need to do a sanity check on the Product Updates Modal, Release section. - We also need to do a sanity check on the Login, Signup, ResetPassword pages. - I think we can merge this Pull Request and continue with our weekly regression, because there are no style changes in this Pull Request, everything should work as expected. ## 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-13 11:05:59 +00:00
export const StyledDeleteIcon = styled(FormIcons.DELETE_ICON)`
${CommonIconStyles}
&& svg {
width: 16px;
height: 16px;
position: relative;
path {
fill: ${(props) => props.theme.colors.propertyPane.iconColor};
}
}
`;
export const StyledCheckbox = styled(Checkbox)<{ disabled?: boolean }>`
cursor: ${(props) => (props.disabled ? "default" : "cursor")};
width: 18px;
feat: Change navigate to UI (#14856) * Initial work to change navigate to UI * Remove console.logs * Adjust default parameters and getters/setters for page dropdown field * change url field getter so page names are not showm * Remove ../ from the imports Remove unnecessary todo * Add check for undefined fields * Add validations for url/page name, add error message * Make height auto to accommodate the flexible size of query param text box * Update dropdown list of pages when page names are updated * Set tab to url when a url has been entered, else default to page * Add feature tests * Add check on null value in isValueValidURL to ensure it does not crash the app * Remove unused ref * Fix bug when switch is selected and a new page addition let to page crash * Initial work to change navigate to UI * Remove console.logs * Adjust default parameters and getters/setters for page dropdown field * change url field getter so page names are not showm * Remove ../ from the imports Remove unnecessary todo * Add check for undefined fields * Add validations for url/page name, add error message * Make height auto to accommodate the flexible size of query param text box * Update dropdown list of pages when page names are updated * Set tab to url when a url has been entered, else default to page * Add feature tests * Add check on null value in isValueValidURL to ensure it does not crash the app * Remove unused ref * Fix bug when switch is selected and a new page addition let to page crash * Fix types and imports * Update the tests * Add ref back to the code Co-authored-by: Aishwarya UR <aishwarya@appsmith.com>
2022-09-16 04:30:16 +00:00
${CommonIconStyles}
`;
export const StyledNavigateToFieldWrapper = styled.div`
display: flex;
justify-content: space-between;
height: auto;
`;
export const StyledDividerContainer = styled.div`
width: 1%;
margin-top: 9px;
`;
export const StyledNavigateToFieldsContainer = styled.div`
width: 95%;
`;