@mxenabled/mxui 2.2.0 → 2.2.2

package/README.md

@@ -3,7 +3,23 @@ In order to run the project you will need to make sure that you have yarn instal
 
 1. Install [yarn](https://yarnpkg.com/getting-started/install)
 1. From the project root dir, run `yarn` or `yarn install` to install dependencies
-1. To start the project run `yarn dev` (the project should automatically run in the browser)
+1. To start the project run `yarn dev` (the project should automatically run in the browser, showing the storybook docs)
+
+## Questions/Help
+
+There are several places you can get answers to your questions:
+- this readme document
+- the changelog file in this repo
+- the storybook documentation: [introduction](https://mxui.kube.qa.internal.mx/?path=/docs/introduction--docs), [contributing](https://mxui.kube.qa.internal.mx/?path=/docs/contributing--docs), [theming](https://mxui.kube.qa.internal.mx/?path=/docs/mxui-components-theming--docs)
+- the #design-system slack channel. don't be shy.
+
+## Using this Library
+
+The QA storybook containing the latest changes is [accessible here](https://mxui.kube.qa.internal.mx/?path=/docs/introduction--docs). (you need to be connected to the vpn to view this since it is in the qa environment)
+
+Follow the setup instructions found in the storybook.
+
+Teams are currently adding components as needed, so the list in storybook right now is what has been built so far. Follow the instructions in [the contributing section](https://mxui.kube.qa.internal.mx/?path=/docs/contributing--docs) of the storybook docs to add to this project.
 
 ## Contributing
 
@@ -18,14 +34,6 @@ Shipit will handle version bumping based on the specified flag (major, minor, or
 
 > **Note:** If an alpha version is to be published, update the package version to include a pre-release identifier like `1.2.3-alpha.1` or `1.2.3-v1` and run the `publish:nodejs-npmregistry` job to publish that alpha version.
 
-## Using this Library
-
-The QA storybook containing the latest changes is [accessible here](https://mxui.kube.qa.internal.mx/?path=/docs/introduction--docs).
-
-Follow the setup instructions found in 
-
-Teams are currently adding components as needed, so the list in storybook right now is what has been built so far.
-
 ## Upgrading from 1.x to 2.x
 This major change introcuces a number of breaking changes due to dependency upgrades for React 19 and MUI 7. It also 
 includes removal of deprected components and theme values.

package/dist/components/daterangepicker/small/DatePickerShortcutsSmall.d.ts

@@ -0,0 +1,8 @@
+import { default as React } from 'react';
+import { DateRange, PickersShortcutsProps } from '@mui/x-date-pickers-pro';
+interface DatePickerShortcutsSmallProps extends PickersShortcutsProps<DateRange<Date>> {
+    selectLabel: string;
+    selected?: string;
+}
+declare const DatePickerShortcutsSmall: React.FC<DatePickerShortcutsSmallProps>;
+export default DatePickerShortcutsSmall;

package/dist/components/daterangepicker/small/DateRangePickerSmall.d.ts

@@ -0,0 +1,4 @@
+import { DateRange } from '@mui/x-date-pickers-pro';
+import { PickersLayoutProps } from '@mui/x-date-pickers/PickersLayout';
+declare const DateRangePickerSmallLayout: (props: PickersLayoutProps<DateRange<Date>>) => import("react/jsx-runtime").JSX.Element;
+export default DateRangePickerSmallLayout;