You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using TypeScript, Prettier (1.17.0) and styled-components in a CRA app. When I define the prop types of my styled components inline, I end up with constructs like these:
constComponent=styled.div<{prop1?: Type;prop2?: Type;}>` /* Some styles here... */`;
The above is the formatting chosen by Prettier. However, CRA's ESLint config doesn't seem to agree:
Line 1: Unexpected newline between template tag and template literal no-unexpected-multiline [no-unexpected-multiline]
This means that when I use the pattern above, it is impossible for me to use ESLint and create-react-app together without getting linter errors. It would be cool if the no-unexpected-multiline rule could be either disabled or configured to not trigger in the cases that Prettier creates.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in 5 days if no further activity occurs.
I am using TypeScript, Prettier (1.17.0) and
styled-components
in a CRA app. When I define the prop types of my styled components inline, I end up with constructs like these:The above is the formatting chosen by Prettier. However, CRA's ESLint config doesn't seem to agree:
This means that when I use the pattern above, it is impossible for me to use ESLint and create-react-app together without getting linter errors. It would be cool if the
no-unexpected-multiline
rule could be either disabled or configured to not trigger in the cases that Prettier creates.The text was updated successfully, but these errors were encountered: