Andy Ray

Ah, looks like this extension ignores checkstyle preferences and only registers itself for the "java" language mode: https://github.com/jdneo/vscode-checkstyle/blob/f194657a25096d8872dd76fdaf7a54ceb44fcfae/src/extension.ts#L47 My file is "Apex" language mode (which checkstyle fully supports, since it's...

Jest introduced this significant breaking change to `.toHaveProperty()` that broke a fair amount of my tests. It's not just a period. This fails, even though there's no period in the...

[The changelog](https://github.com/jestjs/jest/blob/main/CHANGELOG.md) does not seem to mention this significant breaking change to this method. When was it introduced?

Hmm - I didn't realize that the `.` property path feature existed since the beginning. I upgrade Jest from 27 to 29 and hit this issue. I think my issue...

If anyone else stumbles across this, the workaround is to wrap the key in square brackets, like ```expect({ 'vec4[3]: float, vec3': {} }).toHaveProperty(['vec4[3]: float, vec3']);```

@kemilbeltre There is a hack you can use in the linked Stackoverflow question. I couldn't use that for my app so I sadly had to refactor my core domain types...

Doesn't seem stale given the reports (stackoverflow, this report, and https://github.com/colinhacks/zod/issues/2598)

I ended up filing a duplicate, but also to make it explicit, implied in this bug is the fibonnaci example in 3.5.2 will crash from too many calculations if you...

On a Mac, I've installed my root cert to my jvm certs file, for me it's: ``` /Library/Java/JavaVirtualMachines/zulu-11.jdk/Contents/Home/lib/security/cacerts ``` I can verify my expected cert is in that file with:...

@Bug-Reaper I'm less familiar with TSL overall so I might not be adding the right context. In the issue you linked - it takes a different approach than TSL. It...