Dave Beshero

@tlycken I was able to work around that issue in `react-css-modules` (it was something on my end causing the issue). However, switching from `react-css-modules` to this library, I'm greeted with...

@Igor-Vuk you might have to specify in your .babelrc file... ```js { "env": { "test": { "plugins": [ ["react-css-modules", { "context": }] ] } } } ```

I'm wondering if `context` gets resolved to a relative path under the hood or if it's expected that we pass in the resolved path.

Digging through [here](https://github.com/gajus/babel-plugin-react-css-modules/blob/master/src/requireCssModule.js#L88), it doesn't look like it resolves an absolute path for the context you pass in.

@GianlucaVeschi unless I'm misunderstanding something, the PR associated with this issue was merged in late 2022: https://github.com/mermaid-js/mermaid/pull/3706 You can now specify `Title` for all diagrams.

@JedWatson Just pinging because it looks like others were pinging with lowercase `jedwatson` which didn't appear to be performing the `@mention`. Many have been needing the changes either in this...

@MartinHaeusler We ran into that issue too with the v1 update, introduced by this commit https://github.com/JedWatson/react-codemirror/commit/339b5975724cde338301f4c6842f2d52b4773e76. Your best bet is to either... 1. use ^0.3.0 and suffer the deprecation warnings...

@marcioaffonso I think this lib only manages a focus state locally. Outside of the current bug for prop value comparison, it is fully controlled. But yeah, other than downgrading or...

@chillaq, thank you. I did see that example. However, `const treatments = useTreatments([featureName]);` is at the core of that example, where you still must pass in an array of one...

Draft PR: https://github.com/splitio/react-client/pull/70