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

Make component compatible with styled-components providing the className for parent element #209

Closed

Conversation

karolisgrinkevicius
Copy link
Contributor

@karolisgrinkevicius karolisgrinkevicius commented Nov 21, 2019

Description

Make component compatible with emotion and styled-components providing the className for parent element.

Motivation

Previously this component wasn't compatible neither with emotion css in js nor styled-components due to the class name being set for child element.

* chore: cleanup and dependencies upgrade

* chore: add commitlint and lint-staged

* ci(release): add semantic release workflow

* chore(lint): add prettier

* chore(deps): upgraded dependencies

* feat(tests): migrate tests suite to jest

* chore(typescript): add youtube player types

* chore(tests): add tests github action workflow

* ci(release): add pre-release channel

* ci(tests): fix test on ci

* fix(config): fix some typos

* chore(commits): add commitizen cli

* ci(commits): add commitlint to pull requests

* chore(git): remove .vscode folder

* chore(deps): upgraded dependencies
@ruisaraiva19
Copy link
Collaborator

@karolisgrinkevicius we have updated the codebase and this code is now outdated.
Can you please resolve the conflicts and update the tests as well?
Thanks.

@karolisgrinkevicius-home24

@ruisaraiva19 I have rebased and fixed all the conflicts. Please take a look. Thanks.

@ruisaraiva19
Copy link
Collaborator

@karolisgrinkevicius-home24 we are using the canary branch as our default branch going forward. Can you please update this PR accordingly?

@karolisgrinkevicius
Copy link
Contributor Author

@ruisaraiva19 thanks for the info, I have created another PR against canary origin branch here: #226 hence let's move the conversation directly in there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants