Skip to content
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.

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

0.2.1 defaultProps migration introduces breaking change #562

Closed
mmaloon opened this issue May 17, 2024 · 4 comments
Closed

0.2.1 defaultProps migration introduces breaking change #562

mmaloon opened this issue May 17, 2024 · 4 comments

Comments

@mmaloon
Copy link

mmaloon commented May 17, 2024

Describe the bug
Release 0.2.1 introduces bug where explicitly passing undefined as a className causes an error

Reproducible test case
Codepen Demo

Expected behavior
This has potential to break existing code. Maybe revert and save for a major release?

This code works for version 0.2.0 but not on 0.2.1
<FontAwesomeIcon className={undefined} icon={faUser} />

@mmaloon
Copy link
Author

mmaloon commented May 17, 2024

Didn't realize there is already a pull-request discussing this issue: #559

@shehi
Copy link

shehi commented May 21, 2024

Regardless of any PRs, this issue should exist.

The usage of .split() function contradicts TS typing of className props which is nullable:

image

@robmadole
Copy link
Member

Thanks, I'll take a look at this.

@robmadole
Copy link
Member

Just released 0.2.2. Please give this a try.

CrispyBaguette pushed a commit to CrispyBaguette/wasm-palette-converter that referenced this issue Nov 8, 2024
This PR contains the following updates:

| Package | Type | Update | Change |
|---|---|---|---|
| [@fortawesome/react-fontawesome](https://github.com/FortAwesome/react-fontawesome) | dependencies | minor | [`^0.1.19` -> `^0.2.0`](https://renovatebot.com/diffs/npm/@fortawesome%2freact-fontawesome/0.1.19/0.2.2) |

---

### Release Notes

<details>
<summary>FortAwesome/react-fontawesome (@&#8203;fortawesome/react-fontawesome)</summary>

### [`v0.2.2`](https://github.com/FortAwesome/react-fontawesome/blob/HEAD/CHANGELOG.md#022---2024-05-22)

[Compare Source](FortAwesome/react-fontawesome@0.2.1...0.2.2)

##### Fixed

-   Props with nullable/undefined values no longer throw an error [#&#8203;562](FortAwesome/react-fontawesome#562) [#&#8203;560](FortAwesome/react-fontawesome#560)

***

### [`v0.2.1`](https://github.com/FortAwesome/react-fontawesome/blob/HEAD/CHANGELOG.md#021---2024-05-16)

[Compare Source](FortAwesome/react-fontawesome@0.2.0...0.2.1)

##### Changed

-   Remove defaultProps to be compatible with React 19

***

### [`v0.2.0`](https://github.com/FortAwesome/react-fontawesome/blob/HEAD/CHANGELOG.md#020---2022-06-29)

[Compare Source](FortAwesome/react-fontawesome@0.1.19...0.2.0)

##### Added

-   Support for React forwardRef if using React >= 16.3

**Previous [0.1.x change log available here](https://github.com/FortAwesome/react-fontawesome/blob/0.1.x/CHANGELOG.md)**

</details>

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update again.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

---

This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOC4xNDIuNSIsInVwZGF0ZWRJblZlciI6IjM4LjE0Mi41IiwidGFyZ2V0QnJhbmNoIjoibWFzdGVyIiwibGFiZWxzIjpbXX0=-->

Reviewed-on: https://gitea.bruyant.xyz/alexandre/PaletteSwitcher/pulls/44
Co-authored-by: Renovate <[email protected]>
Co-committed-by: Renovate <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants