Rudomanenko Volodymyr
Rudomanenko Volodymyr
no it doesn't reproduce https://user-images.githubusercontent.com/18424848/235316603-a23aaed1-7be1-4c5b-809f-a33f1357f4e6.mp4
I tried `.ts` and it didn't reproduce, only `.tsx`
@michelengelen Honestly I don't fully understand the problem, but I understand that if you remove any influence of `CssVarsProvider` on the row background color, the problem will be solved. This...
well I found something instead of doing this ```javascript const { t } = useTranslation(); const columns = useMemo(() => [ { field: "first_name", headerName: t("first_name") }, { field: "last_name",...
Title of a custom filter operator also doesn't update when switching languages. But if you pass the `Trans` component instead of a simple string, it will update ```javascript const {...
@michelengelen I am not satisfied with my solution Firstly, I don't like using ts-ignore Secondly, I don't like using `renderHeader` because I can't just return translation in the `renderHeader` callback...
### Workaround 2 ```javascript const columnsRef = useRef([ { field: 'title', lazyHeaderName: () => t('title'), headerName: "", } ], []); const apiRef = useGridApiRef(); useLayoutEffect(() => { const forceUpdate =...
Yes, and you can use my sandbox. next is already there
> Is i18n not updating the t function on a language change? The problem is not with i18next but with the `columns` prop. The `columns` prop must keep the reference...
well, I found another workaround to this issue. I can simply reload the page after changing the language