profile
viewpoint
Clement Hoang clemmy @creditkarma Milky Way http://www.clemmy.ninja Create happiness 🌈

clemmy/amusement 2

HackWestern 2015 Winner - Muse hack that plays music corresponding with a user's concentration level.

clemmy/cv 2

My resume for use in the 2B co-op term. Now revised to be my CV.

clemmy/BCQueue 1

Badminton club management software that features queuing and identity functionalities.

clemmy/crowdin-node 1

Nodejs module for accessing Crowdin.net

clemmy/dep-favors 1

Hack the North 2014

andrew-zhou/rfs 0

Restaurant Feedback System

bkauyeung/query-landing-page 0

work in progress

clemmy/2a-resume 0

My old resume.

starteddotansimha/graphql-code-generator

started time in a day

startedgoldbergyoni/javascript-testing-best-practices

started time in 7 days

startedjhnns/rewire

started time in 7 days

startedlabs42io/clean-code-typescript

started time in a month

startedinfluxdata/influxdb

started time in 2 months

starteds0md3v/XSStrike

started time in 2 months

startedalibaba/Alink

started time in 2 months

startedmicrosoft/monaco-editor

started time in 3 months

startedhome-assistant/home-assistant

started time in 3 months

startedGoogleContainerTools/skaffold

started time in 3 months

startedAzure/draft

started time in 3 months

push eventclemmy/emotion

Clement Hoang

commit sha 16743f3bed6a02413194e1a0b37513fd67dac5dd

Re-order bullet points in CSS prop usage

view details

Clement Hoang

commit sha 10ba3fe95e3102f12cb1c9494fecfce483a3d277

Merge branch 'clarify-prefixing-docs' of github.com:clemmy/emotion into clarify-prefixing-docs

view details

push time in 3 months

push eventclemmy/emotion

ajs139

commit sha 9328cd7a329204de29f714ce02d1200185224bbb

Fix printing names of nested shallow-rendered components (#1665) * Introduce broken test case * Fix shallow component snapshots * Update .changeset/great-bears-sing.md Co-Authored-By: Mateusz Burzyński <mateuszburzynski@gmail.com>

view details

Mateusz Burzyński

commit sha b3c5b8de66e42dd2e6459862c9603f012ba01d54

Revert improved support for Enzyme's shallow rendering (#1667) * Revert "Fix printing names of nested shallow-rendered components (#1665)" This reverts commit 9328cd7a329204de29f714ce02d1200185224bbb. * Revert "Improve support for Enzyme's shallow rendering (#1648)" This reverts commit 858c6e70e2aa83d159dba00af16f1e34a6d93fd0. * add changeset

view details

github-actions[bot]

commit sha 04038fdd8a08ac23a99ef14915c6ee446f2bc90a

Version Packages (#1666)

view details

mitchellhamilton

commit sha 037af39ff32d96687c8b897940b63a60e91bfe81

Add Thinkmill to the sponsors because they sponsor my work on Emotion

view details

Clement Hoang

commit sha a7c3d7bdb75349406a2e7f2cfced609abd491674

Merge branch 'master' into clarify-prefixing-docs

view details

push time in 3 months

push eventclemmy/emotion

Clement Hoang

commit sha 0548d604243ec5efef4cb448cfc8c4cc09286836

Mention style prop again

view details

push time in 3 months

Pull request review commentemotion-js/emotion

Clarify Vanilla Emotion auto-prefixing capabilities in documentation

 The ["@emotion/core"](https://www.npmjs.com/package/@emotion/core) package requi  - CSS prop support -  - Similar to the `style` prop but adds support for nested selectors, media queries, and auto-prefixing.

Upon re-reading this part of the code, I realize that I was associating the style prop with the framework agnostic section for some reason. Let me re-add this part.

clemmy

comment created time in 3 months

PR opened emotion-js/emotion

Clarify Vanilla Emotion auto-prefixing capabilities in documentation

Happy Thanksgiving everyone!

<!-- What changes are being made? (What feature/bug is being fixed here?) --> What:

I made this issue a while back where I had misconceptions about the capabilities of Vanilla Emotion. In this PR, I tidy up the docs a bit to hopefully erase these misconceptions (at least when read by me!).

<!-- Why are these changes necessary? --> Why:

These changes are needed to help Emotion users understand the capabilities of Vanilla vs React emotion better.

<!-- How were these changes implemented? --> How:

Markdown changes!

<!-- Have you done all of these things? --> Checklist: <!-- add "N/A" to the end of each line that's irrelevant to your changes --> <!-- to check an item, place an "x" in the box like so: "- [x] Documentation" -->

  • [ ] Documentation
  • [ ] Tests
  • [ ] Code complete
  • [ ] Changeset <!-- This is necessary if your changes should release any packages. Run yarn changeset to create a changeset -->

<!-- feel free to add additional comments -->

+4 -4

0 comment

1 changed file

pr created time in 3 months

create barnchclemmy/emotion

branch : clarify-prefixing-docs

created branch time in 3 months

fork clemmy/emotion

👩‍🎤 CSS-in-JS library designed for high performance style composition

https://emotion.sh/

fork in 3 months

startedAPIs-guru/graphql-voyager

started time in 4 months

startedhasura/graphql-engine

started time in 4 months

fork clemmy/snowtooth

A real GraphQL API for a fake ski resort. 🏔🚡⛷

https://snowtooth.moonhighway.com

fork in 4 months

fork clemmy/snowtooth

A real GraphQL API for a fake ski resort. 🏔🚡⛷

https://snowtooth.moonhighway.com

fork in 4 months

fork clemmy/summit-bootcamp

Course Materials for the Advanced GraphQL Bootcamp at GraphQL Summit 🎉

https://www.moonhighway.com

fork in 4 months

startedgraphqlworkshop/summit-bootcamp

started time in 4 months

startedwojtekmaj/react-lifecycle-methods-diagram

started time in 4 months

startedrvagg/node-worker-farm

started time in 4 months

startedjdneo/vscode-leetcode

started time in 5 months

issue commentemotion-js/emotion

How to get auto-prefixing with vanilla Emotion?

I'll throw up a PR :)

clemmy

comment created time in 5 months

issue commentemotion-js/emotion

How to get auto-prefixing with vanilla Emotion?

Ah, thank you for the quick responses! So if I understand correctly, vanilla emotion should support auto-prefixing out of the box? :) We should totally be selling this feature!

My main misconception probably comes from: https://emotion.sh/docs/introduction#react where it says

CSS prop support - Similar to the style prop but adds support for nested selectors, media queries, and auto-prefixing.

Perhaps we should move the auto-prefixing support to the Framework Agnostic section 😄

clemmy

comment created time in 5 months

issue openedemotion-js/emotion

How to get auto-prefixing with vanilla Emotion?

<!-- Documentation issues are a great way for newcomers to contribute to open source projects! If you have time please consider opening a Pull Request with your documentation changes. -->

Description:

I've re-read multiple times all the different areas of the documentation that refers to vanilla Emotion usage:

https://emotion.sh/docs/introduction#framework-agnostic https://medium.com/@tkh44/emotion-ad1c45c6d28b https://emotion.sh/docs/install https://emotion.sh/docs/emotion

but I'm confused about what exactly Emotion is doing with the css-decorated template literals and how I can get them to be auto-prefixed. In my build pipeline, I have the autoprefixer plugin set up with PostCSS for the CSS loader, but from what I can see, Emotion does not omit any CSS.

I think it would be nice to:

  1. Describe the architecture about what emotion is doing on a high-level
  2. Walk through a solution for adding vendor prefixes with vanilla emotion

created time in 5 months

starteddonnemartin/system-design-primer

started time in 5 months

startedfacebook/metro

started time in 5 months

startedcmiscm/leonsans

started time in 6 months

more