Celeste Carloni
Celeste Carloni
An error is thrown when having nested template literals with conditional expressions where the CSS property is defined within the expression Given ``` ${(props) => props.isPrimary ? ` color: green;...
When commenting an independent condition expression, styles are still applied ``` const Component = styled.div` /*${({ isRed }) => isRed ? 'color: red' : 'color: green'};*/ `; // Outputs const...
Adding custom selectors to `css` and `styled` definitions will result in a bloated extracted stylesheet. For example, specifying the following creates three unique rules: ``` styled.div` color: blue; // .hash...
**Describe the bug** When creating a story that imports CSS mixins from an external file, story is not created unless we also import `css` **To Reproduce** Steps to reproduce the...
[ESLINT] @compiled/no-exported-css should not throw if exported component makes reference to css({})
Looking at the source code of this ESLint rule [compiled/validate-definition.ts at master · atlassian-labs/compiled](https://github.com/atlassian-labs/compiled/blob/master/packages/eslint-plugin/src/utils/create-no-exported-rule/validate-definition.ts#L143) , it iterates through all of the references to css({}). Example: const foo = css` color:...
**Describe the bug** This is a follow up task from https://github.com/atlassian-labs/compiled/pull/928 When working locally, the stories error as follows  We should include...
TBH, I am not sure if this is a valuable change considering [these devlop issues ](https://github.com/atlassian-labs/compiled/issues/1531). Also, we know that classes starting with `_` are usually Compiled; hence, we can...
A very minor update, devs are not aware of this option