2016-02-15 08:27:41 -06:00
|
|
|
// Global values
|
|
|
|
// --------------------------------------------------
|
|
|
|
|
2017-10-18 00:49:52 -05:00
|
|
|
$theme-name: light;
|
2016-02-15 08:27:41 -06:00
|
|
|
|
|
|
|
// Grays
|
|
|
|
// -------------------------
|
2017-12-19 09:22:41 -06:00
|
|
|
$black: #000;
|
|
|
|
$dark-2: #1e2028;
|
|
|
|
$dark-3: #303133;
|
|
|
|
$dark-4: #35373f;
|
|
|
|
$dark-5: #41444b;
|
|
|
|
$gray-1: #52545c;
|
|
|
|
$gray-2: #767980;
|
|
|
|
$gray-3: #acb6bf;
|
|
|
|
$gray-4: #c7d0d9;
|
|
|
|
$gray-5: #dde4ed;
|
|
|
|
$gray-6: #e9edf2;
|
|
|
|
$gray-7: #f7f8fa;
|
|
|
|
|
|
|
|
$white: #fff;
|
2016-02-15 08:27:41 -06:00
|
|
|
|
|
|
|
// Accent colors
|
|
|
|
// -------------------------
|
2018-07-20 09:02:41 -05:00
|
|
|
$blue: #0083b3;
|
|
|
|
$blue-light: #00a8e6;
|
2017-12-19 09:22:41 -06:00
|
|
|
$green: #3aa655;
|
|
|
|
$red: #d44939;
|
|
|
|
$yellow: #ff851b;
|
|
|
|
$orange: #ff7941;
|
|
|
|
$purple: #9954bb;
|
|
|
|
$variable: $blue;
|
|
|
|
|
|
|
|
$brand-primary: $orange;
|
|
|
|
$brand-success: $green;
|
|
|
|
$brand-warning: $orange;
|
|
|
|
$brand-danger: $red;
|
|
|
|
|
2018-05-25 05:51:27 -05:00
|
|
|
$query-red: $red;
|
|
|
|
$query-green: $green;
|
|
|
|
$query-purple: $purple;
|
|
|
|
$query-orange: $orange;
|
2018-12-03 10:20:02 -06:00
|
|
|
$query-keyword: $blue;
|
2017-12-15 04:01:18 -06:00
|
|
|
|
2016-02-15 08:27:41 -06:00
|
|
|
// Status colors
|
|
|
|
// -------------------------
|
2017-12-19 09:22:41 -06:00
|
|
|
$online: #01a64f;
|
|
|
|
$warn: #f79520;
|
|
|
|
$critical: #ec2128;
|
2016-02-15 08:27:41 -06:00
|
|
|
|
2016-02-15 09:02:58 -06:00
|
|
|
// Scaffolding
|
|
|
|
// -------------------------
|
2017-12-19 09:22:41 -06:00
|
|
|
$body-bg: $gray-7;
|
2018-12-07 14:13:23 -06:00
|
|
|
$page-bg: $gray-7;
|
2019-02-06 08:45:40 -06:00
|
|
|
|
2017-12-19 09:22:41 -06:00
|
|
|
$body-color: $gray-1;
|
2018-02-02 03:18:45 -06:00
|
|
|
$text-color: $gray-1;
|
2018-04-03 02:53:14 -05:00
|
|
|
$text-color-strong: $dark-2;
|
2017-12-19 09:22:41 -06:00
|
|
|
$text-color-weak: $gray-2;
|
|
|
|
$text-color-faint: $gray-4;
|
|
|
|
$text-color-emphasis: $dark-5;
|
2016-02-15 08:27:41 -06:00
|
|
|
|
2016-03-28 06:10:42 -05:00
|
|
|
$text-shadow-faint: none;
|
2017-12-04 06:12:32 -06:00
|
|
|
$textShadow: none;
|
2016-03-28 06:10:42 -05:00
|
|
|
|
2016-02-24 03:32:22 -06:00
|
|
|
// gradients
|
2019-02-06 08:45:40 -06:00
|
|
|
$brand-gradient: linear-gradient(
|
2019-02-06 08:47:03 -06:00
|
|
|
to right,
|
|
|
|
rgba(255, 213, 0, 1) 0%,
|
|
|
|
rgba(255, 68, 0, 1) 99%,
|
2019-02-06 08:45:40 -06:00
|
|
|
rgba(255, 68, 0, 1) 100%
|
|
|
|
);
|
|
|
|
|
2019-01-09 02:42:30 -06:00
|
|
|
$page-gradient: linear-gradient(180deg, $white 10px, $gray-7 100px);
|
2018-11-22 08:34:55 -06:00
|
|
|
$edit-gradient: linear-gradient(-60deg, $gray-7, #f5f6f9 70%, $gray-7 98%);
|
2016-02-24 03:32:22 -06:00
|
|
|
|
2016-02-15 08:27:41 -06:00
|
|
|
// Links
|
|
|
|
// -------------------------
|
2017-12-19 09:22:41 -06:00
|
|
|
$link-color: $gray-1;
|
|
|
|
$link-color-disabled: lighten($link-color, 30%);
|
|
|
|
$link-hover-color: darken($link-color, 20%);
|
2018-07-20 09:02:41 -05:00
|
|
|
$external-link-color: $blue-light;
|
2016-02-15 08:27:41 -06:00
|
|
|
|
|
|
|
// Typography
|
|
|
|
// -------------------------
|
2017-12-19 09:22:41 -06:00
|
|
|
$headings-color: $text-color;
|
|
|
|
$abbr-border-color: $gray-2 !default;
|
|
|
|
$text-muted: $text-color-weak;
|
2016-02-16 03:42:06 -06:00
|
|
|
|
2016-02-19 07:21:57 -06:00
|
|
|
$hr-border-color: $dark-3 !default;
|
2016-02-16 02:42:46 -06:00
|
|
|
|
|
|
|
// Panel
|
|
|
|
// -------------------------
|
2017-12-19 09:22:41 -06:00
|
|
|
$panel-bg: $white;
|
2019-02-06 08:45:40 -06:00
|
|
|
$panel-border: solid 1px $gray-5;
|
2017-12-19 09:22:41 -06:00
|
|
|
$panel-header-hover-bg: $gray-6;
|
2019-01-07 06:56:36 -06:00
|
|
|
$panel-corner: $gray-4;
|
2016-02-16 02:42:46 -06:00
|
|
|
|
2017-12-03 01:11:07 -06:00
|
|
|
// Page header
|
2017-12-05 05:48:16 -06:00
|
|
|
$page-header-bg: linear-gradient(90deg, $white, $gray-7);
|
|
|
|
$page-header-shadow: inset 0px -3px 10px $gray-6;
|
|
|
|
$page-header-border-color: $gray-4;
|
2017-12-03 01:11:07 -06:00
|
|
|
|
2017-12-19 09:22:41 -06:00
|
|
|
$divider-border-color: $gray-2;
|
2016-02-16 02:42:46 -06:00
|
|
|
|
|
|
|
// Graphite Target Editor
|
2017-12-19 09:22:41 -06:00
|
|
|
$tight-form-bg: #eaebee;
|
|
|
|
$tight-form-func-bg: $gray-5;
|
|
|
|
$tight-form-func-highlight-bg: $gray-6;
|
2016-02-15 08:27:41 -06:00
|
|
|
|
2017-10-10 10:57:53 -05:00
|
|
|
$modal-backdrop-bg: $body-bg;
|
2017-12-19 09:22:41 -06:00
|
|
|
$code-tag-bg: $gray-6;
|
|
|
|
$code-tag-border: darken($code-tag-bg, 3%);
|
2016-02-15 08:27:41 -06:00
|
|
|
|
2017-11-23 05:54:12 -06:00
|
|
|
// cards
|
2017-12-05 08:16:06 -06:00
|
|
|
$card-background: linear-gradient(135deg, $gray-6, $gray-5);
|
|
|
|
$card-background-hover: linear-gradient(135deg, $gray-5, $gray-6);
|
2018-01-25 05:17:16 -06:00
|
|
|
$card-shadow: -1px -1px 0 0 hsla(0, 0%, 100%, 0.1), 1px 1px 0 0 rgba(0, 0, 0, 0.1);
|
2016-02-15 08:27:41 -06:00
|
|
|
|
2017-11-23 05:54:12 -06:00
|
|
|
// Lists
|
2017-12-19 09:22:41 -06:00
|
|
|
$list-item-bg: linear-gradient(135deg, $gray-5, $gray-6); //$card-background;
|
|
|
|
$list-item-hover-bg: darken($gray-5, 5%);
|
2017-11-23 05:54:12 -06:00
|
|
|
$list-item-link-color: $text-color;
|
2017-12-19 09:22:41 -06:00
|
|
|
$list-item-shadow: $card-shadow;
|
2019-02-06 08:45:40 -06:00
|
|
|
|
2018-01-31 07:14:11 -06:00
|
|
|
$empty-list-cta-bg: $gray-6;
|
2016-02-15 08:27:41 -06:00
|
|
|
|
2019-02-06 08:45:40 -06:00
|
|
|
// Scrollbars
|
|
|
|
$scrollbarBackground: $gray-5;
|
|
|
|
$scrollbarBackground2: $gray-5;
|
|
|
|
$scrollbarBorder: $gray-4;
|
|
|
|
|
2016-02-15 08:27:41 -06:00
|
|
|
// Tables
|
|
|
|
// -------------------------
|
2017-12-19 09:22:41 -06:00
|
|
|
$table-bg: transparent; // overall background-color
|
|
|
|
$table-bg-accent: $gray-5; // for striping
|
|
|
|
$table-border: $gray-3; // table and cell border
|
2016-02-15 08:27:41 -06:00
|
|
|
|
2018-01-25 05:17:16 -06:00
|
|
|
$table-bg-odd: $gray-6;
|
|
|
|
$table-bg-hover: $gray-5;
|
2017-12-05 05:48:16 -06:00
|
|
|
|
2016-02-15 08:27:41 -06:00
|
|
|
// Buttons
|
|
|
|
// -------------------------
|
2017-12-19 09:22:41 -06:00
|
|
|
$btn-primary-bg: $brand-primary;
|
|
|
|
$btn-primary-bg-hl: lighten($brand-primary, 8%);
|
2016-02-15 08:27:41 -06:00
|
|
|
|
2018-07-20 09:02:41 -05:00
|
|
|
$btn-secondary-bg: $blue;
|
|
|
|
$btn-secondary-bg-hl: lighten($blue, 4%);
|
2016-02-15 08:27:41 -06:00
|
|
|
|
2017-12-19 09:22:41 -06:00
|
|
|
$btn-success-bg: lighten($green, 3%);
|
|
|
|
$btn-success-bg-hl: darken($green, 3%);
|
2016-02-15 08:27:41 -06:00
|
|
|
|
2017-12-19 09:22:41 -06:00
|
|
|
$btn-warning-bg: lighten($orange, 3%);
|
|
|
|
$btn-warning-bg-hl: darken($orange, 3%);
|
2016-02-15 08:27:41 -06:00
|
|
|
|
2017-12-19 09:22:41 -06:00
|
|
|
$btn-danger-bg: lighten($red, 3%);
|
|
|
|
$btn-danger-bg-hl: darken($red, 3%);
|
2016-02-15 08:27:41 -06:00
|
|
|
|
2017-12-19 09:22:41 -06:00
|
|
|
$btn-inverse-bg: $gray-6;
|
|
|
|
$btn-inverse-bg-hl: darken($gray-6, 5%);
|
|
|
|
$btn-inverse-text-color: $gray-1;
|
|
|
|
$btn-inverse-text-shadow: 0 1px 0 rgba(255, 255, 255, 0.4);
|
2016-02-15 08:27:41 -06:00
|
|
|
|
2016-02-19 07:21:57 -06:00
|
|
|
$btn-link-color: $gray-1;
|
2016-02-15 08:27:41 -06:00
|
|
|
|
2019-02-06 08:45:40 -06:00
|
|
|
$iconContainerBackground: $white;
|
|
|
|
|
2017-12-19 09:22:41 -06:00
|
|
|
$btn-divider-left: $gray-4;
|
|
|
|
$btn-divider-right: $gray-7;
|
2016-08-11 11:25:41 -05:00
|
|
|
|
2019-02-06 08:45:40 -06:00
|
|
|
$btn-drag-image: '../img/grab_light.svg';
|
2016-02-15 08:27:41 -06:00
|
|
|
|
|
|
|
// Forms
|
|
|
|
// -------------------------
|
2017-12-19 09:22:41 -06:00
|
|
|
$input-bg: $white;
|
|
|
|
$input-bg-disabled: $gray-5;
|
|
|
|
|
|
|
|
$input-color: $dark-3;
|
|
|
|
$input-border-color: $gray-5;
|
|
|
|
$input-box-shadow: none;
|
|
|
|
$input-border-focus: $blue !default;
|
|
|
|
$input-box-shadow-focus: $blue !default;
|
|
|
|
$input-color-placeholder: $gray-4 !default;
|
|
|
|
$input-label-bg: $gray-5;
|
|
|
|
$input-label-border-color: $gray-5;
|
2018-10-08 06:39:00 -05:00
|
|
|
$input-color-select-arrow: $gray-1;
|
2016-02-15 08:27:41 -06:00
|
|
|
|
2019-02-06 08:45:40 -06:00
|
|
|
// Input placeholder text color
|
|
|
|
$placeholderText: $gray-2;
|
2018-11-11 10:46:40 -06:00
|
|
|
|
2016-02-15 08:27:41 -06:00
|
|
|
// search
|
2017-06-12 14:11:22 -05:00
|
|
|
$search-shadow: 0 5px 30px 0 $gray-4;
|
2017-12-05 05:48:16 -06:00
|
|
|
$search-filter-box-bg: $gray-7;
|
2016-02-15 08:27:41 -06:00
|
|
|
|
2018-05-25 05:51:27 -05:00
|
|
|
// Typeahead
|
|
|
|
$typeahead-shadow: 0 5px 10px 0 $gray-5;
|
2018-12-03 10:20:02 -06:00
|
|
|
$typeahead-selected-bg: $gray-6;
|
|
|
|
$typeahead-selected-color: $yellow;
|
2018-05-25 05:51:27 -05:00
|
|
|
|
2016-02-15 08:27:41 -06:00
|
|
|
// Dropdowns
|
|
|
|
// -------------------------
|
2017-12-19 09:22:41 -06:00
|
|
|
$dropdownBackground: $white;
|
|
|
|
$dropdownBorder: $gray-4;
|
|
|
|
$dropdownDividerTop: $gray-6;
|
|
|
|
$dropdownDividerBottom: $white;
|
2016-02-15 08:27:41 -06:00
|
|
|
|
2017-12-19 09:22:41 -06:00
|
|
|
$dropdownLinkColor: $dark-3;
|
|
|
|
$dropdownLinkColorHover: $link-color;
|
|
|
|
$dropdownLinkColorActive: $link-color;
|
2016-02-15 08:27:41 -06:00
|
|
|
|
2017-12-19 09:22:41 -06:00
|
|
|
$dropdownLinkBackgroundHover: $gray-6;
|
2016-02-15 08:27:41 -06:00
|
|
|
|
|
|
|
// Horizontal forms & lists
|
|
|
|
// -------------------------
|
2017-12-19 09:22:41 -06:00
|
|
|
$horizontalComponentOffset: 180px;
|
2016-02-15 08:27:41 -06:00
|
|
|
|
|
|
|
// Navbar
|
|
|
|
// -------------------------
|
2017-12-19 09:22:41 -06:00
|
|
|
$navbarHeight: 52px;
|
2019-02-06 08:45:40 -06:00
|
|
|
|
2017-12-19 09:22:41 -06:00
|
|
|
$navbarBackground: $white;
|
|
|
|
$navbarBorder: 1px solid $gray-4;
|
|
|
|
$navbarShadow: 0 0 3px #c1c1c1;
|
2016-02-15 08:27:41 -06:00
|
|
|
|
2017-12-19 09:22:41 -06:00
|
|
|
$navbarLinkColor: #444;
|
2016-02-15 08:27:41 -06:00
|
|
|
|
2017-12-19 09:22:41 -06:00
|
|
|
$navbarButtonBackground: lighten($navbarBackground, 3%);
|
2016-02-15 08:27:41 -06:00
|
|
|
$navbarButtonBackgroundHighlight: lighten($navbarBackground, 5%);
|
|
|
|
|
2017-12-19 09:22:41 -06:00
|
|
|
$navbar-button-border: $gray-4;
|
2016-02-15 08:27:41 -06:00
|
|
|
|
2019-02-06 08:45:40 -06:00
|
|
|
// Sidemenu
|
2016-02-15 08:27:41 -06:00
|
|
|
// -------------------------
|
2019-02-06 08:45:40 -06:00
|
|
|
$side-menu-bg: $dark-2;
|
|
|
|
$side-menu-bg-mobile: rgba(0, 0, 0, 0); //$gray-6;
|
|
|
|
$side-menu-item-hover-bg: $gray-1;
|
|
|
|
$side-menu-shadow: 5px 0px 10px -5px $gray-1;
|
|
|
|
$side-menu-link-color: $gray-6;
|
|
|
|
|
|
|
|
// Menu dropdowns
|
|
|
|
// -------------------------
|
|
|
|
$menu-dropdown-bg: $gray-7;
|
|
|
|
$menu-dropdown-hover-bg: $gray-6;
|
|
|
|
$menu-dropdown-shadow: 5px 5px 10px -5px $gray-1;
|
|
|
|
|
|
|
|
// Tabs
|
|
|
|
// -------------------------
|
|
|
|
$tab-border-color: $gray-5;
|
|
|
|
|
|
|
|
// Toolbar
|
|
|
|
$toolbar-bg: white;
|
2016-02-15 08:27:41 -06:00
|
|
|
|
|
|
|
// Form states and alerts
|
|
|
|
// -------------------------
|
2017-12-19 09:22:41 -06:00
|
|
|
$warning-text-color: lighten($orange, 10%);
|
|
|
|
$error-text-color: lighten($red, 10%);
|
|
|
|
$success-text-color: lighten($green, 10%);
|
|
|
|
$info-text-color: $blue;
|
2016-02-15 08:27:41 -06:00
|
|
|
|
2017-12-19 09:22:41 -06:00
|
|
|
$alert-error-bg: linear-gradient(90deg, #d44939, #e04d3d);
|
|
|
|
$alert-success-bg: linear-gradient(90deg, #3aa655, #47b274);
|
|
|
|
$alert-warning-bg: linear-gradient(90deg, #d44939, #e04d3d);
|
2018-07-20 09:02:41 -05:00
|
|
|
$alert-info-bg: $blue;
|
2016-02-15 08:27:41 -06:00
|
|
|
|
2016-04-11 19:33:58 -05:00
|
|
|
// popover
|
2017-12-19 09:22:41 -06:00
|
|
|
$popover-bg: $page-bg;
|
|
|
|
$popover-color: $text-color;
|
|
|
|
$popover-border-color: $gray-5;
|
|
|
|
$popover-shadow: 0 0 20px $white;
|
2017-10-07 03:31:39 -05:00
|
|
|
|
2018-07-20 09:02:41 -05:00
|
|
|
$popover-help-bg: $blue;
|
2017-12-19 09:22:41 -06:00
|
|
|
$popover-help-color: $gray-6;
|
2019-02-06 08:45:40 -06:00
|
|
|
|
2017-12-19 09:22:41 -06:00
|
|
|
$popover-error-bg: $btn-danger-bg;
|
2016-02-15 08:27:41 -06:00
|
|
|
|
|
|
|
// Tooltips and popovers
|
|
|
|
// -------------------------
|
2017-12-19 09:22:41 -06:00
|
|
|
$tooltipColor: $popover-help-color;
|
|
|
|
$tooltipArrowWidth: 5px;
|
|
|
|
$tooltipLinkColor: lighten($popover-help-color, 5%);
|
|
|
|
$graph-tooltip-bg: $gray-5;
|
2016-02-22 04:41:50 -06:00
|
|
|
|
2019-01-23 08:39:13 -06:00
|
|
|
$tooltipBackground: $gray-1;
|
|
|
|
$tooltipColor: $gray-7;
|
2019-01-07 06:05:27 -06:00
|
|
|
$tooltipArrowColor: $tooltipBackground; // Used by Angular tooltip
|
|
|
|
$tooltipBackgroundError: $brand-danger;
|
|
|
|
|
2016-02-15 08:27:41 -06:00
|
|
|
// images
|
2018-01-25 05:17:16 -06:00
|
|
|
$checkboxImageUrl: '../img/checkbox_white.png';
|
2016-03-15 03:15:24 -05:00
|
|
|
|
2017-07-31 07:39:33 -05:00
|
|
|
// info box
|
2018-10-05 01:43:56 -05:00
|
|
|
$info-box-border-color: lighten($blue, 20%);
|
2017-07-31 07:39:33 -05:00
|
|
|
|
2016-05-24 01:11:28 -05:00
|
|
|
// footer
|
2017-12-19 09:22:41 -06:00
|
|
|
$footer-link-color: $gray-3;
|
|
|
|
$footer-link-hover: $dark-5;
|
History and Version Control for Dashboard Updates
A simple version control system for dashboards. Closes #1504.
Goals
1. To create a new dashboard version every time a dashboard is saved.
2. To allow users to view all versions of a given dashboard.
3. To allow users to rollback to a previous version of a dashboard.
4. To allow users to compare two versions of a dashboard.
Usage
Navigate to a dashboard, and click the settings cog. From there, click
the "Changelog" button to be brought to the Changelog view. In this
view, a table containing each version of a dashboard can be seen. Each
entry in the table represents a dashboard version. A selectable
checkbox, the version number, date created, name of the user who created
that version, and commit message is shown in the table, along with a
button that allows a user to restore to a previous version of that
dashboard. If a user wants to restore to a previous version of their
dashboard, they can do so by clicking the previously mentioned button.
If a user wants to compare two different versions of a dashboard, they
can do so by clicking the checkbox of two different dashboard versions,
then clicking the "Compare versions" button located below the dashboard.
From there, the user is brought to a view showing a summary of the
dashboard differences. Each summarized change contains a link that can
be clicked to take the user a JSON diff highlighting the changes line by
line.
Overview of Changes
Backend Changes
- A `dashboard_version` table was created to store each dashboard
version, along with a dashboard version model and structs to represent
the queries and commands necessary for the dashboard version API
methods.
- API endpoints were created to support working with dashboard
versions.
- Methods were added to create, update, read, and destroy dashboard
versions in the database.
- Logic was added to compute the diff between two versions, and
display it to the user.
- The dashboard migration logic was updated to save a "Version
1" of each existing dashboard in the database.
Frontend Changes
- New views
- Methods to pull JSON and HTML from endpoints
New API Endpoints
Each endpoint requires the authorization header to be sent in
the format,
```
Authorization: Bearer <jwt>
```
where `<jwt>` is a JSON web token obtained from the Grafana
admin panel.
`GET "/api/dashboards/db/:dashboardId/versions?orderBy=<string>&limit=<int>&start=<int>"`
Get all dashboard versions for the given dashboard ID. Accepts
three URL parameters:
- `orderBy` String to order the results by. Possible values
are `version`, `created`, `created_by`, `message`. Default
is `versions`. Ordering is always in descending order.
- `limit` Maximum number of results to return
- `start` Position in results to start from
`GET "/api/dashboards/db/:dashboardId/versions/:id"`
Get an individual dashboard version by ID, for the given
dashboard ID.
`POST "/api/dashboards/db/:dashboardId/restore"`
Restore to the given dashboard version. Post body is of
content-type `application/json`, and must contain.
```json
{
"dashboardId": <int>,
"version": <int>
}
```
`GET "/api/dashboards/db/:dashboardId/compare/:versionA...:versionB"`
Compare two dashboard versions by ID for the given
dashboard ID, returning a JSON delta formatted
representation of the diff. The URL format follows
what GitHub does. For example, visiting
[/api/dashboards/db/18/compare/22...33](http://ec2-54-80-139-44.compute-1.amazonaws.com:3000/api/dashboards/db/18/compare/22...33)
will return the diff between versions 22 and 33 for
the dashboard ID 18.
Dependencies Added
- The Go package [gojsondiff](https://github.com/yudai/gojsondiff)
was added and vendored.
2017-05-24 18:14:39 -05:00
|
|
|
|
2017-05-20 11:21:41 -05:00
|
|
|
// json explorer
|
|
|
|
$json-explorer-default-color: black;
|
|
|
|
$json-explorer-string-color: green;
|
|
|
|
$json-explorer-number-color: blue;
|
|
|
|
$json-explorer-boolean-color: red;
|
2017-12-19 09:22:41 -06:00
|
|
|
$json-explorer-null-color: #855a00;
|
2017-05-20 11:21:41 -05:00
|
|
|
$json-explorer-undefined-color: rgb(202, 11, 105);
|
2017-12-19 09:22:41 -06:00
|
|
|
$json-explorer-function-color: #ff20ed;
|
2017-05-20 11:21:41 -05:00
|
|
|
$json-explorer-rotate-time: 100ms;
|
|
|
|
$json-explorer-toggler-opacity: 0.6;
|
|
|
|
$json-explorer-bracket-color: blue;
|
2017-12-19 09:22:41 -06:00
|
|
|
$json-explorer-key-color: #00008b;
|
2017-05-20 11:21:41 -05:00
|
|
|
$json-explorer-url-color: blue;
|
History and Version Control for Dashboard Updates
A simple version control system for dashboards. Closes #1504.
Goals
1. To create a new dashboard version every time a dashboard is saved.
2. To allow users to view all versions of a given dashboard.
3. To allow users to rollback to a previous version of a dashboard.
4. To allow users to compare two versions of a dashboard.
Usage
Navigate to a dashboard, and click the settings cog. From there, click
the "Changelog" button to be brought to the Changelog view. In this
view, a table containing each version of a dashboard can be seen. Each
entry in the table represents a dashboard version. A selectable
checkbox, the version number, date created, name of the user who created
that version, and commit message is shown in the table, along with a
button that allows a user to restore to a previous version of that
dashboard. If a user wants to restore to a previous version of their
dashboard, they can do so by clicking the previously mentioned button.
If a user wants to compare two different versions of a dashboard, they
can do so by clicking the checkbox of two different dashboard versions,
then clicking the "Compare versions" button located below the dashboard.
From there, the user is brought to a view showing a summary of the
dashboard differences. Each summarized change contains a link that can
be clicked to take the user a JSON diff highlighting the changes line by
line.
Overview of Changes
Backend Changes
- A `dashboard_version` table was created to store each dashboard
version, along with a dashboard version model and structs to represent
the queries and commands necessary for the dashboard version API
methods.
- API endpoints were created to support working with dashboard
versions.
- Methods were added to create, update, read, and destroy dashboard
versions in the database.
- Logic was added to compute the diff between two versions, and
display it to the user.
- The dashboard migration logic was updated to save a "Version
1" of each existing dashboard in the database.
Frontend Changes
- New views
- Methods to pull JSON and HTML from endpoints
New API Endpoints
Each endpoint requires the authorization header to be sent in
the format,
```
Authorization: Bearer <jwt>
```
where `<jwt>` is a JSON web token obtained from the Grafana
admin panel.
`GET "/api/dashboards/db/:dashboardId/versions?orderBy=<string>&limit=<int>&start=<int>"`
Get all dashboard versions for the given dashboard ID. Accepts
three URL parameters:
- `orderBy` String to order the results by. Possible values
are `version`, `created`, `created_by`, `message`. Default
is `versions`. Ordering is always in descending order.
- `limit` Maximum number of results to return
- `start` Position in results to start from
`GET "/api/dashboards/db/:dashboardId/versions/:id"`
Get an individual dashboard version by ID, for the given
dashboard ID.
`POST "/api/dashboards/db/:dashboardId/restore"`
Restore to the given dashboard version. Post body is of
content-type `application/json`, and must contain.
```json
{
"dashboardId": <int>,
"version": <int>
}
```
`GET "/api/dashboards/db/:dashboardId/compare/:versionA...:versionB"`
Compare two dashboard versions by ID for the given
dashboard ID, returning a JSON delta formatted
representation of the diff. The URL format follows
what GitHub does. For example, visiting
[/api/dashboards/db/18/compare/22...33](http://ec2-54-80-139-44.compute-1.amazonaws.com:3000/api/dashboards/db/18/compare/22...33)
will return the diff between versions 22 and 33 for
the dashboard ID 18.
Dependencies Added
- The Go package [gojsondiff](https://github.com/yudai/gojsondiff)
was added and vendored.
2017-05-24 18:14:39 -05:00
|
|
|
|
|
|
|
// Changelog and diff
|
|
|
|
// -------------------------
|
2017-12-19 09:22:41 -06:00
|
|
|
$diff-label-bg: $gray-5;
|
|
|
|
$diff-label-fg: $gray-2;
|
History and Version Control for Dashboard Updates
A simple version control system for dashboards. Closes #1504.
Goals
1. To create a new dashboard version every time a dashboard is saved.
2. To allow users to view all versions of a given dashboard.
3. To allow users to rollback to a previous version of a dashboard.
4. To allow users to compare two versions of a dashboard.
Usage
Navigate to a dashboard, and click the settings cog. From there, click
the "Changelog" button to be brought to the Changelog view. In this
view, a table containing each version of a dashboard can be seen. Each
entry in the table represents a dashboard version. A selectable
checkbox, the version number, date created, name of the user who created
that version, and commit message is shown in the table, along with a
button that allows a user to restore to a previous version of that
dashboard. If a user wants to restore to a previous version of their
dashboard, they can do so by clicking the previously mentioned button.
If a user wants to compare two different versions of a dashboard, they
can do so by clicking the checkbox of two different dashboard versions,
then clicking the "Compare versions" button located below the dashboard.
From there, the user is brought to a view showing a summary of the
dashboard differences. Each summarized change contains a link that can
be clicked to take the user a JSON diff highlighting the changes line by
line.
Overview of Changes
Backend Changes
- A `dashboard_version` table was created to store each dashboard
version, along with a dashboard version model and structs to represent
the queries and commands necessary for the dashboard version API
methods.
- API endpoints were created to support working with dashboard
versions.
- Methods were added to create, update, read, and destroy dashboard
versions in the database.
- Logic was added to compute the diff between two versions, and
display it to the user.
- The dashboard migration logic was updated to save a "Version
1" of each existing dashboard in the database.
Frontend Changes
- New views
- Methods to pull JSON and HTML from endpoints
New API Endpoints
Each endpoint requires the authorization header to be sent in
the format,
```
Authorization: Bearer <jwt>
```
where `<jwt>` is a JSON web token obtained from the Grafana
admin panel.
`GET "/api/dashboards/db/:dashboardId/versions?orderBy=<string>&limit=<int>&start=<int>"`
Get all dashboard versions for the given dashboard ID. Accepts
three URL parameters:
- `orderBy` String to order the results by. Possible values
are `version`, `created`, `created_by`, `message`. Default
is `versions`. Ordering is always in descending order.
- `limit` Maximum number of results to return
- `start` Position in results to start from
`GET "/api/dashboards/db/:dashboardId/versions/:id"`
Get an individual dashboard version by ID, for the given
dashboard ID.
`POST "/api/dashboards/db/:dashboardId/restore"`
Restore to the given dashboard version. Post body is of
content-type `application/json`, and must contain.
```json
{
"dashboardId": <int>,
"version": <int>
}
```
`GET "/api/dashboards/db/:dashboardId/compare/:versionA...:versionB"`
Compare two dashboard versions by ID for the given
dashboard ID, returning a JSON delta formatted
representation of the diff. The URL format follows
what GitHub does. For example, visiting
[/api/dashboards/db/18/compare/22...33](http://ec2-54-80-139-44.compute-1.amazonaws.com:3000/api/dashboards/db/18/compare/22...33)
will return the diff between versions 22 and 33 for
the dashboard ID 18.
Dependencies Added
- The Go package [gojsondiff](https://github.com/yudai/gojsondiff)
was added and vendored.
2017-05-24 18:14:39 -05:00
|
|
|
|
2017-12-19 09:22:41 -06:00
|
|
|
$diff-arrow-color: $dark-3;
|
|
|
|
$diff-group-bg: $gray-7;
|
History and Version Control for Dashboard Updates
A simple version control system for dashboards. Closes #1504.
Goals
1. To create a new dashboard version every time a dashboard is saved.
2. To allow users to view all versions of a given dashboard.
3. To allow users to rollback to a previous version of a dashboard.
4. To allow users to compare two versions of a dashboard.
Usage
Navigate to a dashboard, and click the settings cog. From there, click
the "Changelog" button to be brought to the Changelog view. In this
view, a table containing each version of a dashboard can be seen. Each
entry in the table represents a dashboard version. A selectable
checkbox, the version number, date created, name of the user who created
that version, and commit message is shown in the table, along with a
button that allows a user to restore to a previous version of that
dashboard. If a user wants to restore to a previous version of their
dashboard, they can do so by clicking the previously mentioned button.
If a user wants to compare two different versions of a dashboard, they
can do so by clicking the checkbox of two different dashboard versions,
then clicking the "Compare versions" button located below the dashboard.
From there, the user is brought to a view showing a summary of the
dashboard differences. Each summarized change contains a link that can
be clicked to take the user a JSON diff highlighting the changes line by
line.
Overview of Changes
Backend Changes
- A `dashboard_version` table was created to store each dashboard
version, along with a dashboard version model and structs to represent
the queries and commands necessary for the dashboard version API
methods.
- API endpoints were created to support working with dashboard
versions.
- Methods were added to create, update, read, and destroy dashboard
versions in the database.
- Logic was added to compute the diff between two versions, and
display it to the user.
- The dashboard migration logic was updated to save a "Version
1" of each existing dashboard in the database.
Frontend Changes
- New views
- Methods to pull JSON and HTML from endpoints
New API Endpoints
Each endpoint requires the authorization header to be sent in
the format,
```
Authorization: Bearer <jwt>
```
where `<jwt>` is a JSON web token obtained from the Grafana
admin panel.
`GET "/api/dashboards/db/:dashboardId/versions?orderBy=<string>&limit=<int>&start=<int>"`
Get all dashboard versions for the given dashboard ID. Accepts
three URL parameters:
- `orderBy` String to order the results by. Possible values
are `version`, `created`, `created_by`, `message`. Default
is `versions`. Ordering is always in descending order.
- `limit` Maximum number of results to return
- `start` Position in results to start from
`GET "/api/dashboards/db/:dashboardId/versions/:id"`
Get an individual dashboard version by ID, for the given
dashboard ID.
`POST "/api/dashboards/db/:dashboardId/restore"`
Restore to the given dashboard version. Post body is of
content-type `application/json`, and must contain.
```json
{
"dashboardId": <int>,
"version": <int>
}
```
`GET "/api/dashboards/db/:dashboardId/compare/:versionA...:versionB"`
Compare two dashboard versions by ID for the given
dashboard ID, returning a JSON delta formatted
representation of the diff. The URL format follows
what GitHub does. For example, visiting
[/api/dashboards/db/18/compare/22...33](http://ec2-54-80-139-44.compute-1.amazonaws.com:3000/api/dashboards/db/18/compare/22...33)
will return the diff between versions 22 and 33 for
the dashboard ID 18.
Dependencies Added
- The Go package [gojsondiff](https://github.com/yudai/gojsondiff)
was added and vendored.
2017-05-24 18:14:39 -05:00
|
|
|
|
2017-12-19 09:22:41 -06:00
|
|
|
$diff-json-bg: $gray-5;
|
|
|
|
$diff-json-fg: $gray-2;
|
History and Version Control for Dashboard Updates
A simple version control system for dashboards. Closes #1504.
Goals
1. To create a new dashboard version every time a dashboard is saved.
2. To allow users to view all versions of a given dashboard.
3. To allow users to rollback to a previous version of a dashboard.
4. To allow users to compare two versions of a dashboard.
Usage
Navigate to a dashboard, and click the settings cog. From there, click
the "Changelog" button to be brought to the Changelog view. In this
view, a table containing each version of a dashboard can be seen. Each
entry in the table represents a dashboard version. A selectable
checkbox, the version number, date created, name of the user who created
that version, and commit message is shown in the table, along with a
button that allows a user to restore to a previous version of that
dashboard. If a user wants to restore to a previous version of their
dashboard, they can do so by clicking the previously mentioned button.
If a user wants to compare two different versions of a dashboard, they
can do so by clicking the checkbox of two different dashboard versions,
then clicking the "Compare versions" button located below the dashboard.
From there, the user is brought to a view showing a summary of the
dashboard differences. Each summarized change contains a link that can
be clicked to take the user a JSON diff highlighting the changes line by
line.
Overview of Changes
Backend Changes
- A `dashboard_version` table was created to store each dashboard
version, along with a dashboard version model and structs to represent
the queries and commands necessary for the dashboard version API
methods.
- API endpoints were created to support working with dashboard
versions.
- Methods were added to create, update, read, and destroy dashboard
versions in the database.
- Logic was added to compute the diff between two versions, and
display it to the user.
- The dashboard migration logic was updated to save a "Version
1" of each existing dashboard in the database.
Frontend Changes
- New views
- Methods to pull JSON and HTML from endpoints
New API Endpoints
Each endpoint requires the authorization header to be sent in
the format,
```
Authorization: Bearer <jwt>
```
where `<jwt>` is a JSON web token obtained from the Grafana
admin panel.
`GET "/api/dashboards/db/:dashboardId/versions?orderBy=<string>&limit=<int>&start=<int>"`
Get all dashboard versions for the given dashboard ID. Accepts
three URL parameters:
- `orderBy` String to order the results by. Possible values
are `version`, `created`, `created_by`, `message`. Default
is `versions`. Ordering is always in descending order.
- `limit` Maximum number of results to return
- `start` Position in results to start from
`GET "/api/dashboards/db/:dashboardId/versions/:id"`
Get an individual dashboard version by ID, for the given
dashboard ID.
`POST "/api/dashboards/db/:dashboardId/restore"`
Restore to the given dashboard version. Post body is of
content-type `application/json`, and must contain.
```json
{
"dashboardId": <int>,
"version": <int>
}
```
`GET "/api/dashboards/db/:dashboardId/compare/:versionA...:versionB"`
Compare two dashboard versions by ID for the given
dashboard ID, returning a JSON delta formatted
representation of the diff. The URL format follows
what GitHub does. For example, visiting
[/api/dashboards/db/18/compare/22...33](http://ec2-54-80-139-44.compute-1.amazonaws.com:3000/api/dashboards/db/18/compare/22...33)
will return the diff between versions 22 and 33 for
the dashboard ID 18.
Dependencies Added
- The Go package [gojsondiff](https://github.com/yudai/gojsondiff)
was added and vendored.
2017-05-24 18:14:39 -05:00
|
|
|
|
2017-12-19 09:22:41 -06:00
|
|
|
$diff-json-added: lighten(desaturate($green, 30%), 10%);
|
|
|
|
$diff-json-deleted: desaturate($red, 35%);
|
History and Version Control for Dashboard Updates
A simple version control system for dashboards. Closes #1504.
Goals
1. To create a new dashboard version every time a dashboard is saved.
2. To allow users to view all versions of a given dashboard.
3. To allow users to rollback to a previous version of a dashboard.
4. To allow users to compare two versions of a dashboard.
Usage
Navigate to a dashboard, and click the settings cog. From there, click
the "Changelog" button to be brought to the Changelog view. In this
view, a table containing each version of a dashboard can be seen. Each
entry in the table represents a dashboard version. A selectable
checkbox, the version number, date created, name of the user who created
that version, and commit message is shown in the table, along with a
button that allows a user to restore to a previous version of that
dashboard. If a user wants to restore to a previous version of their
dashboard, they can do so by clicking the previously mentioned button.
If a user wants to compare two different versions of a dashboard, they
can do so by clicking the checkbox of two different dashboard versions,
then clicking the "Compare versions" button located below the dashboard.
From there, the user is brought to a view showing a summary of the
dashboard differences. Each summarized change contains a link that can
be clicked to take the user a JSON diff highlighting the changes line by
line.
Overview of Changes
Backend Changes
- A `dashboard_version` table was created to store each dashboard
version, along with a dashboard version model and structs to represent
the queries and commands necessary for the dashboard version API
methods.
- API endpoints were created to support working with dashboard
versions.
- Methods were added to create, update, read, and destroy dashboard
versions in the database.
- Logic was added to compute the diff between two versions, and
display it to the user.
- The dashboard migration logic was updated to save a "Version
1" of each existing dashboard in the database.
Frontend Changes
- New views
- Methods to pull JSON and HTML from endpoints
New API Endpoints
Each endpoint requires the authorization header to be sent in
the format,
```
Authorization: Bearer <jwt>
```
where `<jwt>` is a JSON web token obtained from the Grafana
admin panel.
`GET "/api/dashboards/db/:dashboardId/versions?orderBy=<string>&limit=<int>&start=<int>"`
Get all dashboard versions for the given dashboard ID. Accepts
three URL parameters:
- `orderBy` String to order the results by. Possible values
are `version`, `created`, `created_by`, `message`. Default
is `versions`. Ordering is always in descending order.
- `limit` Maximum number of results to return
- `start` Position in results to start from
`GET "/api/dashboards/db/:dashboardId/versions/:id"`
Get an individual dashboard version by ID, for the given
dashboard ID.
`POST "/api/dashboards/db/:dashboardId/restore"`
Restore to the given dashboard version. Post body is of
content-type `application/json`, and must contain.
```json
{
"dashboardId": <int>,
"version": <int>
}
```
`GET "/api/dashboards/db/:dashboardId/compare/:versionA...:versionB"`
Compare two dashboard versions by ID for the given
dashboard ID, returning a JSON delta formatted
representation of the diff. The URL format follows
what GitHub does. For example, visiting
[/api/dashboards/db/18/compare/22...33](http://ec2-54-80-139-44.compute-1.amazonaws.com:3000/api/dashboards/db/18/compare/22...33)
will return the diff between versions 22 and 33 for
the dashboard ID 18.
Dependencies Added
- The Go package [gojsondiff](https://github.com/yudai/gojsondiff)
was added and vendored.
2017-05-24 18:14:39 -05:00
|
|
|
|
2017-12-19 09:22:41 -06:00
|
|
|
$diff-json-old: #5a372a;
|
|
|
|
$diff-json-new: #664e33;
|
History and Version Control for Dashboard Updates
A simple version control system for dashboards. Closes #1504.
Goals
1. To create a new dashboard version every time a dashboard is saved.
2. To allow users to view all versions of a given dashboard.
3. To allow users to rollback to a previous version of a dashboard.
4. To allow users to compare two versions of a dashboard.
Usage
Navigate to a dashboard, and click the settings cog. From there, click
the "Changelog" button to be brought to the Changelog view. In this
view, a table containing each version of a dashboard can be seen. Each
entry in the table represents a dashboard version. A selectable
checkbox, the version number, date created, name of the user who created
that version, and commit message is shown in the table, along with a
button that allows a user to restore to a previous version of that
dashboard. If a user wants to restore to a previous version of their
dashboard, they can do so by clicking the previously mentioned button.
If a user wants to compare two different versions of a dashboard, they
can do so by clicking the checkbox of two different dashboard versions,
then clicking the "Compare versions" button located below the dashboard.
From there, the user is brought to a view showing a summary of the
dashboard differences. Each summarized change contains a link that can
be clicked to take the user a JSON diff highlighting the changes line by
line.
Overview of Changes
Backend Changes
- A `dashboard_version` table was created to store each dashboard
version, along with a dashboard version model and structs to represent
the queries and commands necessary for the dashboard version API
methods.
- API endpoints were created to support working with dashboard
versions.
- Methods were added to create, update, read, and destroy dashboard
versions in the database.
- Logic was added to compute the diff between two versions, and
display it to the user.
- The dashboard migration logic was updated to save a "Version
1" of each existing dashboard in the database.
Frontend Changes
- New views
- Methods to pull JSON and HTML from endpoints
New API Endpoints
Each endpoint requires the authorization header to be sent in
the format,
```
Authorization: Bearer <jwt>
```
where `<jwt>` is a JSON web token obtained from the Grafana
admin panel.
`GET "/api/dashboards/db/:dashboardId/versions?orderBy=<string>&limit=<int>&start=<int>"`
Get all dashboard versions for the given dashboard ID. Accepts
three URL parameters:
- `orderBy` String to order the results by. Possible values
are `version`, `created`, `created_by`, `message`. Default
is `versions`. Ordering is always in descending order.
- `limit` Maximum number of results to return
- `start` Position in results to start from
`GET "/api/dashboards/db/:dashboardId/versions/:id"`
Get an individual dashboard version by ID, for the given
dashboard ID.
`POST "/api/dashboards/db/:dashboardId/restore"`
Restore to the given dashboard version. Post body is of
content-type `application/json`, and must contain.
```json
{
"dashboardId": <int>,
"version": <int>
}
```
`GET "/api/dashboards/db/:dashboardId/compare/:versionA...:versionB"`
Compare two dashboard versions by ID for the given
dashboard ID, returning a JSON delta formatted
representation of the diff. The URL format follows
what GitHub does. For example, visiting
[/api/dashboards/db/18/compare/22...33](http://ec2-54-80-139-44.compute-1.amazonaws.com:3000/api/dashboards/db/18/compare/22...33)
will return the diff between versions 22 and 33 for
the dashboard ID 18.
Dependencies Added
- The Go package [gojsondiff](https://github.com/yudai/gojsondiff)
was added and vendored.
2017-05-24 18:14:39 -05:00
|
|
|
|
2017-12-19 09:22:41 -06:00
|
|
|
$diff-json-changed-fg: $gray-6;
|
History and Version Control for Dashboard Updates
A simple version control system for dashboards. Closes #1504.
Goals
1. To create a new dashboard version every time a dashboard is saved.
2. To allow users to view all versions of a given dashboard.
3. To allow users to rollback to a previous version of a dashboard.
4. To allow users to compare two versions of a dashboard.
Usage
Navigate to a dashboard, and click the settings cog. From there, click
the "Changelog" button to be brought to the Changelog view. In this
view, a table containing each version of a dashboard can be seen. Each
entry in the table represents a dashboard version. A selectable
checkbox, the version number, date created, name of the user who created
that version, and commit message is shown in the table, along with a
button that allows a user to restore to a previous version of that
dashboard. If a user wants to restore to a previous version of their
dashboard, they can do so by clicking the previously mentioned button.
If a user wants to compare two different versions of a dashboard, they
can do so by clicking the checkbox of two different dashboard versions,
then clicking the "Compare versions" button located below the dashboard.
From there, the user is brought to a view showing a summary of the
dashboard differences. Each summarized change contains a link that can
be clicked to take the user a JSON diff highlighting the changes line by
line.
Overview of Changes
Backend Changes
- A `dashboard_version` table was created to store each dashboard
version, along with a dashboard version model and structs to represent
the queries and commands necessary for the dashboard version API
methods.
- API endpoints were created to support working with dashboard
versions.
- Methods were added to create, update, read, and destroy dashboard
versions in the database.
- Logic was added to compute the diff between two versions, and
display it to the user.
- The dashboard migration logic was updated to save a "Version
1" of each existing dashboard in the database.
Frontend Changes
- New views
- Methods to pull JSON and HTML from endpoints
New API Endpoints
Each endpoint requires the authorization header to be sent in
the format,
```
Authorization: Bearer <jwt>
```
where `<jwt>` is a JSON web token obtained from the Grafana
admin panel.
`GET "/api/dashboards/db/:dashboardId/versions?orderBy=<string>&limit=<int>&start=<int>"`
Get all dashboard versions for the given dashboard ID. Accepts
three URL parameters:
- `orderBy` String to order the results by. Possible values
are `version`, `created`, `created_by`, `message`. Default
is `versions`. Ordering is always in descending order.
- `limit` Maximum number of results to return
- `start` Position in results to start from
`GET "/api/dashboards/db/:dashboardId/versions/:id"`
Get an individual dashboard version by ID, for the given
dashboard ID.
`POST "/api/dashboards/db/:dashboardId/restore"`
Restore to the given dashboard version. Post body is of
content-type `application/json`, and must contain.
```json
{
"dashboardId": <int>,
"version": <int>
}
```
`GET "/api/dashboards/db/:dashboardId/compare/:versionA...:versionB"`
Compare two dashboard versions by ID for the given
dashboard ID, returning a JSON delta formatted
representation of the diff. The URL format follows
what GitHub does. For example, visiting
[/api/dashboards/db/18/compare/22...33](http://ec2-54-80-139-44.compute-1.amazonaws.com:3000/api/dashboards/db/18/compare/22...33)
will return the diff between versions 22 and 33 for
the dashboard ID 18.
Dependencies Added
- The Go package [gojsondiff](https://github.com/yudai/gojsondiff)
was added and vendored.
2017-05-24 18:14:39 -05:00
|
|
|
$diff-json-changed-num: $gray-4;
|
2019-02-06 08:45:40 -06:00
|
|
|
|
2017-12-19 09:22:41 -06:00
|
|
|
$diff-json-icon: $gray-4;
|
2018-07-20 09:02:41 -05:00
|
|
|
|
|
|
|
//Submenu
|
|
|
|
$variable-option-bg: $blue-light;
|
2018-11-16 06:02:29 -06:00
|
|
|
|
|
|
|
//Switch Slider
|
|
|
|
// -------------------------
|
|
|
|
$switch-bg: $white;
|
|
|
|
$switch-slider-color: $gray-7;
|
|
|
|
$switch-slider-off-bg: $gray-5;
|
|
|
|
$switch-slider-on-bg: linear-gradient(90deg, $yellow, $red);
|
|
|
|
$switch-slider-shadow: 0 0 3px $dark-5;
|
2018-11-16 09:35:04 -06:00
|
|
|
|
|
|
|
//Checkbox
|
|
|
|
// -------------------------
|
|
|
|
$checkbox-bg: $gray-6;
|
|
|
|
$checkbox-border: 1px solid $gray-3;
|
|
|
|
$checkbox-checked-bg: linear-gradient(0deg, $yellow, $red);
|
|
|
|
$checkbox-color: $gray-7;
|
2018-11-28 08:51:45 -06:00
|
|
|
|
|
|
|
//Panel Edit
|
|
|
|
// -------------------------
|
2018-12-16 12:30:48 -06:00
|
|
|
$panel-editor-shadow: 0px 0px 8px $gray-3;
|
2018-11-28 08:51:45 -06:00
|
|
|
$panel-editor-side-menu-shadow: drop-shadow(0 0 2px $gray-3);
|
|
|
|
$panel-editor-viz-item-shadow: 0 0 4px $gray-3;
|
|
|
|
$panel-editor-viz-item-border: 1px solid $gray-3;
|
|
|
|
$panel-editor-viz-item-shadow-hover: 0 0 4px $blue-light;
|
|
|
|
$panel-editor-viz-item-border-hover: 1px solid $blue-light;
|
|
|
|
$panel-editor-viz-item-bg: $white;
|
|
|
|
$panel-editor-tabs-line-color: $dark-5;
|
|
|
|
$panel-editor-viz-item-bg-hover: lighten($blue, 62%);
|
2018-11-30 07:14:23 -06:00
|
|
|
|
2019-01-29 08:37:22 -06:00
|
|
|
$panel-options-group-border: none;
|
|
|
|
$panel-options-group-header-bg: $gray-5;
|
2018-12-13 09:02:14 -06:00
|
|
|
|
2018-11-30 07:14:23 -06:00
|
|
|
$panel-grid-placeholder-bg: lighten($blue, 62%);
|
|
|
|
$panel-grid-placeholder-shadow: 0 0 4px $blue-light;
|
2018-12-07 07:59:38 -06:00
|
|
|
|
2018-12-06 13:55:01 -06:00
|
|
|
// logs
|
|
|
|
$logs-color-unkown: $gray-5;
|
2018-12-07 10:15:46 -06:00
|
|
|
|
|
|
|
// toggle-group
|
2018-12-07 14:13:23 -06:00
|
|
|
$button-toggle-group-btn-active-bg: $brand-primary;
|
|
|
|
$button-toggle-group-btn-active-shadow: inset 0 0 4px $white;
|
2018-12-07 10:15:46 -06:00
|
|
|
$button-toggle-group-btn-seperator-border: 1px solid $gray-6;
|
2018-12-18 10:20:09 -06:00
|
|
|
|
|
|
|
$vertical-resize-handle-bg: $gray-4;
|
|
|
|
$vertical-resize-handle-dots: $gray-3;
|
|
|
|
$vertical-resize-handle-dots-hover: $gray-2;
|