Isaiah Thomason

First off, thank you **_so much_** for adding a codesandbox. Plus the example code. Makes life much easier. Ugh. Yeah that really bites. The issue is that TypeScript is trying...

**_UPDATE_** Here's another workaround that I discovered: ```typescript const useStyles2 = createUseStyles((theme) => ({ SectionTitle: { color: theme.color as string, // Bullet "&:before": { content: (props: JssProps) => `"${props.number}"`, border:...

Another update. (This update likely won't interest anyone searching for workarounds/fixes.) I played around with this code, and apparently it produces the same error: ```typescript const useStyles = createUseStyles((theme) =>...

@pip8786 Are you getting this same exact error? Or are you just talking about the re-ordering of parameters?

Do you have a code snippet for more context?

Okay, thanks. And just for clarity... Let's say your props were named `MyProps`. Would the error go away if, for that code block, you did something like this: ```typescript const...

> Yes that fixes it but like I said, this was one simple example of many places where this errors out. Yes, I understand. I was mainly asking to get...

Yeah. I guess I'm not surprised. This is a pretty bothersome bind that TypeScript puts us in. I really really hoping it gets resolved in the near future.

@heyymarco Hmmmmm. This does seem a little strange to me. However, I'm able to use string arrays without any errors in our test file. Do you have a reproducible repo...

Hey @heyymarco. What I was saying was that both JS and TS seem to work fine in our tests. That's why I was asking if you had a reproducible repo...