baseui 10.0.0 → 10.3.0

package/tokens/colors.js.flow

@@ -14,7 +14,7 @@ const colors: ColorTokensT = {
   gray200: '#E2E2E2',
   gray300: '#CBCBCB',
   gray400: '#AFAFAF',
-  gray500: '#757575',
+  gray500: '#6B6B6B',
   gray600: '#545454',
   gray700: '#333333',
   gray800: '#1F1F1F',
@@ -55,14 +55,14 @@ const colors: ColorTokensT = {
   yellow300: '#FFCF70',
   yellow400: '#FFC043',
   yellow500: '#BC8B2C',
-  yellow600: '#997328',
+  yellow600: '#996F00',
   yellow700: '#674D1B',
 
   green50: '#E6F2ED',
   green100: '#ADDEC9',
   green200: '#66D19E',
   green300: '#06C167',
-  green400: '#05944F',
+  green400: '#048848',
   green500: '#03703C',
   green600: '#03582F',
   green700: '#10462D',

package/tree-view/tree-view.js

@@ -150,8 +150,6 @@ function TreeView(props) {
         break;
 
       default:
-        e.preventDefault();
-
         if (timeOutRef.current !== null) {
           clearTimeout(timeOutRef.current);
         }

package/tree-view/tree-view.js.flow

@@ -113,7 +113,6 @@ export default function TreeView(props: TreeViewPropsT) {
         );
         break;
       default:
-        e.preventDefault();
         if (timeOutRef.current !== null) {
           clearTimeout(timeOutRef.current);
         }

package/es/utils/get-bui-id.js

@@ -1,33 +0,0 @@
-/*
-Copyright (c) Uber Technologies, Inc.
-
-This source code is licensed under the MIT license found in the
-LICENSE file in the root directory of this source tree.
-*/
-
-/**
- * For aria and other attributes like htmlFor, we often need
- * to attach identifiers to elements. Making `id` a required
- * prop in our components shifts this burden to our customers
- * but it's nice to try to automatically provide these unique
- * ids when possible.
- *
- * Generating unique IDs that match across server/client renders
- * is a hard problem that doesn't have any perfect solutions
- * currently [1] [2]. UUIDs/Math.random will never match, whereas
- * auto-incrementing IDs may work if server and client render
- * exactly the same DOM, so that's what we'll use here. If this
- * is insufficient for users they can apply ids manually.
- *
- * One other technique that we can use internally is to do a
- * setState in componentDidMount or something similar, so that
- * these ids are only used client-side, but this could of course
- * have perf implications.
- *
- * [1] https://github.com/facebook/react/issues/5867
- * [2] https://github.com/reactjs/rfcs/pull/32/files
- */
-let id = 0;
-export default function getBuiId() {
-  return `bui-${++id}`;
-}

package/esm/utils/get-bui-id.js

@@ -1,33 +0,0 @@
-/*
-Copyright (c) Uber Technologies, Inc.
-
-This source code is licensed under the MIT license found in the
-LICENSE file in the root directory of this source tree.
-*/
-
-/**
- * For aria and other attributes like htmlFor, we often need
- * to attach identifiers to elements. Making `id` a required
- * prop in our components shifts this burden to our customers
- * but it's nice to try to automatically provide these unique
- * ids when possible.
- *
- * Generating unique IDs that match across server/client renders
- * is a hard problem that doesn't have any perfect solutions
- * currently [1] [2]. UUIDs/Math.random will never match, whereas
- * auto-incrementing IDs may work if server and client render
- * exactly the same DOM, so that's what we'll use here. If this
- * is insufficient for users they can apply ids manually.
- *
- * One other technique that we can use internally is to do a
- * setState in componentDidMount or something similar, so that
- * these ids are only used client-side, but this could of course
- * have perf implications.
- *
- * [1] https://github.com/facebook/react/issues/5867
- * [2] https://github.com/reactjs/rfcs/pull/32/files
- */
-var id = 0;
-export default function getBuiId() {
-  return "bui-".concat(++id);
-}

package/utils/get-bui-id.js

@@ -1,41 +0,0 @@
-"use strict";
-
-Object.defineProperty(exports, "__esModule", {
-  value: true
-});
-exports.default = getBuiId;
-
-/*
-Copyright (c) Uber Technologies, Inc.
-
-This source code is licensed under the MIT license found in the
-LICENSE file in the root directory of this source tree.
-*/
-
-/**
- * For aria and other attributes like htmlFor, we often need
- * to attach identifiers to elements. Making `id` a required
- * prop in our components shifts this burden to our customers
- * but it's nice to try to automatically provide these unique
- * ids when possible.
- *
- * Generating unique IDs that match across server/client renders
- * is a hard problem that doesn't have any perfect solutions
- * currently [1] [2]. UUIDs/Math.random will never match, whereas
- * auto-incrementing IDs may work if server and client render
- * exactly the same DOM, so that's what we'll use here. If this
- * is insufficient for users they can apply ids manually.
- *
- * One other technique that we can use internally is to do a
- * setState in componentDidMount or something similar, so that
- * these ids are only used client-side, but this could of course
- * have perf implications.
- *
- * [1] https://github.com/facebook/react/issues/5867
- * [2] https://github.com/reactjs/rfcs/pull/32/files
- */
-var id = 0;
-
-function getBuiId() {
-  return "bui-".concat(++id);
-}

package/utils/get-bui-id.js.flow

@@ -1,39 +0,0 @@
-/*
-Copyright (c) Uber Technologies, Inc.
-
-This source code is licensed under the MIT license found in the
-LICENSE file in the root directory of this source tree.
-*/
-// @flow
-
-/**
- * For aria and other attributes like htmlFor, we often need
- * to attach identifiers to elements. Making `id` a required
- * prop in our components shifts this burden to our customers
- * but it's nice to try to automatically provide these unique
- * ids when possible.
- *
- * Generating unique IDs that match across server/client renders
- * is a hard problem that doesn't have any perfect solutions
- * currently [1] [2]. UUIDs/Math.random will never match, whereas
- * auto-incrementing IDs may work if server and client render
- * exactly the same DOM, so that's what we'll use here. If this
- * is insufficient for users they can apply ids manually.
- *
- * One other technique that we can use internally is to do a
- * setState in componentDidMount or something similar, so that
- * these ids are only used client-side, but this could of course
- * have perf implications.
- *
- * [1] https://github.com/facebook/react/issues/5867
- * [2] https://github.com/reactjs/rfcs/pull/32/files
- */
-let id = 0;
-
-export default function getBuiId() {
-  return `bui-${++id}`;
-}
-
-declare var __DEV__: boolean;
-declare var __NODE__: boolean;
-declare var __BROWSER__: boolean;