Skip to content

Conversation

@davidacevedo
Copy link
Collaborator

  • Bug fix
  • New feature
  • Chore
  • Breaking change
  • There is an open issue which this change addresses
  • I have read the CONTRIBUTING document.
  • My commits follow the Git Commit Guidelines
  • My code follows the code style of this project.
  • My change requires a change to the documentation.
    • I have updated the documentation accordingly.
  • My change requires a change to Typescript typings.
    • I have updated the typings accordingly.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

davidacevedo and others added 7 commits February 3, 2023 16:19
This will make us follow React best practices and depend on libraries that are expecting ref to exist
…efining them as such

Tests were failing because the top level component was a wrapper vs the actual component that was exposed. This also makes it so defaultProps and PropTypes are attached to the actual component exported.
@davidacevedo davidacevedo force-pushed the nodeUpdate branch 2 times, most recently from 60358f3 to a8ad998 Compare February 4, 2023 07:14
@github-actions
Copy link
Contributor

github-actions bot commented Feb 4, 2023

Released prerelease version 9.1.6-nodeUpdate-9a70a59.0.
You may now run npm install reactstrap@nodeUpdate

strategy:
matrix:
node-version: [12.x, 14.x, 16.x]
node-version: [14.x, 16.x]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we can add node 18.x also.

@illiteratewriter illiteratewriter mentioned this pull request Oct 6, 2023
14 tasks
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

Successfully merging this pull request may close these issues.

4 participants