Anton Kastritskii
Anton Kastritskii
I came across two more cases which eventually should end up in either/or FAQ/gotchas sections on the website - class name extraction - workaround for components using React Portal ##...
It's been a while, since most work is done in the next branch and what is left is the documentation I would like to propose a way to tackle it....
Hi and thank you for the issue! This should be pretty easy to implement. An alternative implementation can be done by introducing a single field `patterns: string[]`. Either way the...
@in19farkt про написание стилей все верно, можно писать стиле как эксклюзивно в отдельных css файлах как в стандартном подходе с css-modules, так и в js файлах как те же `styled-components`....
Friendly ping @wuweiweiwu @weirDozzz Should this be merged?
If you want to have support in vim/neovim I strongly recommend not to lean in towards a single LSP client plugin like coc.nvim. Instead if you have a standalone LSP...
> Maybe a better default would then be to not traverse at all (i.e. stopDir = cwd) or maybe stop whenever a package.json is found in the currently traversed directory?...
> Why though? Stuff like a linter or other directly project related things should generally always run in one of two contexts anyway: > - in the whole repo context,...
@d-fischer You are correct. I was thinking about a case where for example a configuration would not be found in a workspaces project root due to the cwd being a...
All of the above sounds totally reasonable. Thanks for expanding on it 👍