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

#212 - remove theming #225

Merged
merged 3 commits into from
Aug 3, 2017
Merged

#212 - remove theming #225

merged 3 commits into from
Aug 3, 2017

Conversation

tkh44
Copy link
Member

@tkh44 tkh44 commented Aug 2, 2017

Putting this up early to get more eyes on it.

Checklist:

  • Documentation
  • Tests
  • Code complete

- first pass
background-color: #ffd43b;
color: #8c81d8;
height: 64px;
font-size: 32px;
}

<span
className="glamor-0 glamor-1"
className="glamor-0 glamor-1 glamor-2 glamor-3"
Copy link
Member Author

Choose a reason for hiding this comment

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

@mitchellhamilton I'm not sure how to interpret these snapshot diffs. Do they look right to you?

Copy link
Member

Choose a reason for hiding this comment

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

They don't, there should only be two classes on each component.

Copy link
Member Author

Choose a reason for hiding this comment

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

This is the actual output on a web page. Maybe this will have a clue.

image

Copy link
Member Author

@tkh44 tkh44 Aug 3, 2017

Choose a reason for hiding this comment

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

Notice the difference in the length of the hash.

Copy link
Member Author

Choose a reason for hiding this comment

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

This is due to wrapping the components with withTheme I believe. I tested this out on the browser and it works as expected.

Copy link
Member

Choose a reason for hiding this comment

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

Yes, that's correct because they're wrapped in withTheme so more components are rendered and the class is added for using components as selectors.

Now that I think about it, we might want to always add the class for using components as selectors because in this example OneComponent will have color: yellow; when rendered inside of SomeComponent but AnotherComponent will not.

const OneComponent = styled.div`
  display: flex;
`
const AnotherComponent = styled(OneComponent)`
  background-color: hotpink;
`
const SomeComponent = styled.div`
  ${OneComponent} {
    color: yellow;
  }
`

Copy link
Member Author

Choose a reason for hiding this comment

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

Do you think I should hold up merging this for that fix or is it something we can separate?

Copy link
Member

Choose a reason for hiding this comment

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

I already pushed a fix to this branch 😀

@codecov-io
Copy link

codecov-io commented Aug 2, 2017

Codecov Report

Merging #225 into master will decrease coverage by 0.11%.
The diff coverage is 100%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #225      +/-   ##
==========================================
- Coverage   90.39%   90.27%   -0.12%     
==========================================
  Files          22       20       -2     
  Lines         979      967      -12     
  Branches      265      262       -3     
==========================================
- Hits          885      873      -12     
  Misses         76       76              
  Partials       18       18
Impacted Files Coverage Δ
src/react/index.js 100% <100%> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update cbc09e5...fed2a14. Read the comment docs.

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.

3 participants