Skip to content

Update Changelog (v10.6.0) #1466

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
kof merged 2 commits into from
Mar 14, 2021
Merged

Update Changelog (v10.6.0) #1466

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2103982
Update Changelog (v10.6.0)
ITenthusiasm Mar 11, 2021
0ae85a7
Apply Requested Changes (Part 1)
ITenthusiasm Mar 12, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
31 changes: 28 additions & 3 deletions changelog.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,10 +4,35 @@ Since you are interested in what happens next, in case, you work for a for-profi

---

### Bug fixes

### Improvements

- [jss] `Styles` now supports `ClassNames`, `Props`/`Data`, and `Theme` as type parameters (eg. `Styles<Names, Data, Theme>`). [1460](https://github.com/cssinjs/jss/pull/1460)
- [react-jss] `withStyles` and `createUseStyles` now support `ClassNames`, `Props`, and `Theme` as type parameters (eg. `createUseStyles<Names, Props, Theme>`). [1460](https://github.com/cssinjs/jss/pull/1460)
- [react-jss] `useStyles` finally expects the correct argument type: a `Props` object with an optional `Theme` property (both determined from `createUseStyles`). [1460](https://github.com/cssinjs/jss/pull/1460)

### Breaking Changes

- [react-jss] `Theme` is no longer the first generic type parameter for `createUseStyles`. [1460](https://github.com/cssinjs/jss/pull/1460)
- There are two main ways to tell TypeScript your `Theme`'s type without reaching over the other type parameters:

Using the function argument.

```typescript
const useStyles = createUseStyles(theme: Theme => ({
ruleName: { /* ... */ };
}))
```

Using the object argument with a function. (You will only need to specify the `Theme` type once.)

```typescript
const useStyles = createUseStyles({
ruleName: ({theme}: {theme: Theme}) => ({
/* ... */
})
})
```

## 10.5.1 (2021-1-23)

### Bug fixes
Expand All @@ -34,7 +59,7 @@ Since you are interested in what happens next, in case, you work for a for-profi
- [*] Remove test files from the package [1406](https://github.com/cssinjs/jss/pull/1406)
- [*] Upgrade rollup [1426](https://github.com/cssinjs/jss/pull/1426)
- [*] Upgrade flow to 0.138.0 [1425](https://github.com/cssinjs/jss/pull/1425)
- [jss-plugin-default-unit] aAdd gap unit [1403](https://github.com/cssinjs/jss/pull/1403)
- [jss-plugin-default-unit] Add gap unit [1403](https://github.com/cssinjs/jss/pull/1403)
- [jss-plugin-default-unit] Add default units to logical properties [1415](https://github.com/cssinjs/jss/pull/1415)
- [jss] Improve deleteRule() performance [1424](https://github.com/cssinjs/jss/pull/1424)

Expand Down
⚡