Skip to content

Commit cbdea02

Browse files
committed
[Fix] missing classNames from helpers
1 parent 66a710c commit cbdea02

File tree

2 files changed

+23
-11
lines changed

2 files changed

+23
-11
lines changed

CONTRIBUTING.md

+17-11
Original file line numberDiff line numberDiff line change
@@ -1,18 +1,22 @@
11
# Contributing
22

3-
Thanks for your interest in contributing to `react-tailwindcss-datepicker`! Please take a moment to review this document **before submitting a pull request**.
3+
Thanks for your interest in contributing to `react-tailwindcss-datepicker`! Please take a moment to
4+
review this document **before submitting a pull request**.
45

5-
- [Pull requests](#pull-requests)
6-
- [Installation](#installation)
7-
- [Coding standards](#coding-standards)
8-
- [Running playground](#running-playgrounds)
9-
- [Before you make a Pull Request](#before-you-make-a-pull-request)
6+
- [Pull requests](#pull-requests)
7+
- [Installation](#installation)
8+
- [Coding standards](#coding-standards)
9+
- [Running playground](#running-playgrounds)
10+
- [Before you make a Pull Request](#before-you-make-a-pull-request)
1011

1112
## Pull requests
1213

1314
**Please ask first before starting work on any significant new features.**
1415

15-
It's never a fun experience to have your pull request declined after investing a lot of time and effort into a new feature. To avoid this from happening, we request that contributors create [an issue](https://github.com/onesine/react-tailwindcss-datepicker/issues) to first discuss any significant new features.
16+
It's never a fun experience to have your pull request declined after investing a lot of time and
17+
effort into a new feature. To avoid this from happening, we request that contributors create
18+
[an issue](https://github.com/onesine/react-tailwindcss-datepicker/issues) to first discuss any
19+
significant new features.
1620

1721
## Installation
1822

@@ -24,8 +28,8 @@ yarn install
2428

2529
## Coding standards
2630

27-
We use `prettier` for making sure that the codebase is formatted consistently.
28-
To automatically fix any style violations in your code, you can run:
31+
We use `prettier` for making sure that the codebase is formatted consistently. To automatically fix
32+
any style violations in your code, you can run:
2933

3034
**Using yarn**
3135

@@ -61,16 +65,18 @@ npm dev
6165

6266
## Before you make a Pull Request
6367

64-
We recommend to run these scripts in sequence before you make your commit message amd open a Pull Request
68+
We recommend to run these scripts in sequence before you make your commit message amd open a Pull
69+
Request
6570

6671
**Let's clean the code first**
72+
6773
```sh
6874
yarn pret:fix
6975
```
7076

7177
**Test a build of your changes**
78+
7279
```sh
7380
yarn build
7481

7582
```
76-

src/helpers/index.ts

+6
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,11 @@ import dayjs from "dayjs";
22
import weekday from "dayjs/plugin/weekday";
33

44
dayjs.extend(weekday);
5+
6+
export function classNames(...classes: (false | null | undefined | string)[]) {
7+
return classes.filter(Boolean).join(" ");
8+
}
9+
510
export function getTextColorByPrimaryColor(color: string) {
611
switch (color) {
712
case "blue":
@@ -165,6 +170,7 @@ export function getNumberOfDay(dayString: string, i18n: string, startWeekOn?: st
165170
}
166171
}
167172
);
173+
168174
return number;
169175
}
170176

0 commit comments

Comments
 (0)