Type error: Type 'TFunctionResult' is not assignable to type 'ReactNode'. #1795

HT-Moh · 2022-04-13T21:21:40Z

Describe the bug

You must provide a clear and concise description of what the bug is.

Occurs in next-i18next version

11.0.0

Steps to reproduce

update to react 18

Expected behaviour

You must provide a clear and concise description of what you expected to happen.

Screenshots

Additional context

This seems to be due to the following two issues
DefinitelyTyped/DefinitelyTyped#46691
DefinitelyTyped/DefinitelyTyped#56210

Solution

pumping react-i18next to the last version which contain the commit

HT-Moh · 2022-04-14T06:54:06Z

The following solution worked for me:
Update packages react and react-dom and types

 "react": "^18.0.0",
 "react-dom": "^18.0.0",
 @types/react": "^18.0.4",
 @types/react-dom": "^18.0.0"

Add the following to package.json

"resolutions": {
    "react-i18next": ">=11.16.4"
  }

azuken · 2022-05-02T10:06:46Z

"resolutions": {
"react-i18next": ">=11.16.4"
}

This is a workaround fix, will an update be available soon ?

EDIT : And this is not working anyway

quertenmont · 2022-05-05T14:49:40Z

I am having the same issue and the working around is indeed not working

qjnz · 2022-05-05T21:15:03Z

I have the same issue

I am having the same issue and the working around is indeed not working

I am having the same issue by using the latest package react-i18next v11.16.8

MouzamSadiq · 2022-05-11T11:04:22Z

place "as string " to it . eg {t."dashboard.title,"dashboad") as string}

phankietit · 2022-05-22T11:41:04Z

Fix by update rn i18next version: Here

adriandmitroca · 2022-05-25T20:28:02Z

Still broken in latest release (11.16.9): Type 'TFunctionResult' is not assignable to type 'ReactNode'.

bedcoding · 2022-05-30T02:14:15Z

I also had the same error when applying TypeScript in i18n.

Type 'TFunctionResult' is not assignable to type 'ReactNode'.
  Type 'object' is not assignable to type 'ReactNode'.
    Type '{}' is missing the following properties from type 'ReactPortal': key, children, type, propsts(2322)

So I modified it as follows.

{t("base.content.no")}
=> {t<string>("base.content.no")}

or

{t("brand.button.management")}
=> {`${t("brand.button.management")}`}

marcoXbresciani · 2022-06-10T07:04:24Z

{${t("brand.button.management")}}

This one is working for me.

react-i18next ^11.17.1
i18next ^21.6.16

See i18next/next-i18next#1795 (comment)

keremcanb · 2022-06-15T07:35:09Z

I'm getting this error if it is only used like this:

import i18n from 'i18next';

i18n.t('text.example')

No problems with this:

import { useTranslation } from 'react-i18next';

const { t } = useTranslation();

t('text.example')

Shackey666 · 2022-07-08T13:38:56Z

Hello, I still have this bug on my side too.

package.json:

peerDep: {
"i18next": "^21.8.11",
"react": "^18.2.0",
"react-dom": "^18.2.0",
"react-i18next": "^11.18.0",
}

devDependencies: {
"@types/react": "^18.0.14",
"@types/react-dom": "^18.0.5",
}

issue example: {t('cart.step.regular')} with const { t } = useTranslation();

Any other solutions than the one proposed before?

HT-Moh · 2022-07-14T08:08:32Z

The other solution is to update all packages to the last version and remove the devDependencies entry, for me the following versions work

"react": "^18.2.0",
"react-dom": "^18.2.0",

 "@types/react": "^18.0.15",
 "@types/react-dom": "^18.0.6",

update all eslint and it's plugins
what works for me last versions

    "eslint": "^8.19.0",
    "eslint-config-prettier": "^8.5.0",
    "eslint-plugin-jsx-a11y": "^6.6.0",
    "eslint-plugin-prettier": "^4.2.1",
    "eslint-plugin-react": "^7.30.1",
    "eslint-plugin-react-hooks": "^4.6.0",
    "eslint-plugin-security": "^1.5.0",
    "eslint-plugin-simple-import-sort": "^7.0.0",
    "eslint-plugin-sonarjs": "^0.13.0",
    "eslint-plugin-unicorn": "^43.0.1",

to check the package that needs to be updated run yarn outdated
I hope this helps.

sigespweb22 · 2022-09-09T14:08:40Z

Correção por atualização rn i18next version: Aqui

It worked for me. Thanks

Dam998 · 2022-09-20T22:21:25Z

you can do something like that too:

export type i18translateType = {
  t: (key: string | TemplateStringsArray | (string | TemplateStringsArray)[], options?: string | TOptions<StringMap> | undefined) => string
}

const component = (props: ...) => {
  const { t }: i18translateType = useTranslation();
  ...
  
  return <div>
    ...
    <p>{t("text")}</p>
    ...
    <button>{t("dashboard")}</button>
  </div>
}

layerok · 2022-09-21T12:41:03Z

updating typescript to ^4.8.3 helped me

MarcelGeo · 2022-10-07T08:53:58Z

If I am using withTranslation() HOC, fix in newest version is not available. Same error:

(property) placeholder?: ReactNode
Type 'TFunctionResult' is not assignable to type 'ReactNode'

OnkelTem · 2022-10-09T13:20:02Z

I don't quite understand what this mess is all about. Could the author provide an explanation?

Here is a mini-demo of the problem: TypeScript Sandbox

import { TFunction as TFunctionNext } from 'next-i18next'
import { TFunction as TFunctionReact } from 'react-i18next'

type Foo = {
  title: React.ReactNode
}

function barNext(foo: Foo, t: TFunctionNext) {
    foo.title = t('Prodict title') 
//  ^^^^^^^^^
//  ERROR:
//   Type 'TFunctionResult' is not assignable to type 'ReactNode'.
//      Type 'object' is not assignable to type 'ReactNode'.(2322)
}

function barReact(foo: Foo, t: TFunctionReact) {
    foo.title = t('Prodict title')
}

Conclusions (for TS 4.7.4 & 4.8.4 that I both tried):

TFunction from react-i18next doesn't produce any problems.
TFunction from next-i18next is the culprit.

Can it be just fixed?

Meanwhile, in such circumstances I would just change all TFunction imports to react-i18next

OnkelTem · 2022-10-09T13:24:09Z

@HT-Moh I see this one is closed. Well, should I file a new report?

I downgraded i18n packages in previous commit (3604038), but these versions have defects in Typescipt typings: i18next/next-i18next#1795 Instead of the default hook, let's use a wrapper with enforced correct types everywhere.

ivansvlv · 2022-10-21T09:59:49Z

I was just migrating the app to React 18 and latest TypeScript and faced the same issue.

"dependencies" : {
    "i18next": "^22.0.1",
    "i18next-browser-languagedetector": "^6.1.8",
    "i18next-http-backend": "^1.4.4",
    "react": "^18.2.0",
    "react-dom": "^18.2.0",
    "react-i18next": "^12.0.0",
},
"devDependencies": {
    "@types/react": "^18.0.21",
    "@types/react-dom": "^18.0.6",
    "@typescript-eslint/eslint-plugin": "^5.40.1",
    "@typescript-eslint/parser": "^5.40.1",
    "eslint": "^8.25.0",
    "eslint-config-airbnb": "^19.0.4",
    "eslint-config-prettier": "^8.5.0",
    "eslint-plugin-import": "^2.26.0",
    "eslint-plugin-jsx-a11y": "^6.6.1",
    "eslint-plugin-react": "^7.31.10",
    "eslint-plugin-react-hooks": "^4.6.0",
    "typescript": "^4.8.4",
}

const { t } = useTranslation('footer');

            <div>
              <Link to="/terms-conditions">{t('links.terms-conditions')}</Link>
              <Link to="/privacy-policy">{t('links.privacy-policy')}</Link>
            </div>

This t() usage type error:

Type 'DefaultTFuncReturn' is not assignable to type 'ReactI18NextChild | Iterable<ReactI18NextChild>'.ts(2322) index.d.ts(47, 5): The expected type comes from property 'children' which is declared here on type 'IntrinsicAttributes & LinkProps & RefAttributes<HTMLAnchorElement>'

However, I can see relevant type definitions that should allow this. Similar error is noticed with general JSX tags:

  const { t } = useTranslation(['login', 'errors']);

        <LoginHeader>
          <h1 className={style.login__title}>{t('login:signin.title')}</h1>
          <p className={style.login__paragraph}>{t('login:signin.subtitle')}</p>
        </LoginHeader>

Type 'DefaultTFuncReturn' is not assignable to type 'ReactI18NextChild | Iterable<ReactI18NextChild>'.ts(2322) index.d.ts(47, 5): The expected type comes from property 'children' which is declared here on type 'DetailedHTMLProps<HTMLAttributes<HTMLHeadingElement>, HTMLHeadingElement>'

I've already tried to remove package-lock.json and node_modules to have a clean install, but it didn't help.

fitimbytyqi · 2022-10-21T11:47:13Z

I was just migrating the app to React 18 and latest TypeScript and faced the same issue.
"dependencies" : {
    "i18next": "^22.0.1",
    "i18next-browser-languagedetector": "^6.1.8",
    "i18next-http-backend": "^1.4.4",
    "react": "^18.2.0",
    "react-dom": "^18.2.0",
    "react-i18next": "^12.0.0",
},
"devDependencies": {
    "@types/react": "^18.0.21",
    "@types/react-dom": "^18.0.6",
    "@typescript-eslint/eslint-plugin": "^5.40.1",
    "@typescript-eslint/parser": "^5.40.1",
    "eslint": "^8.25.0",
    "eslint-config-airbnb": "^19.0.4",
    "eslint-config-prettier": "^8.5.0",
    "eslint-plugin-import": "^2.26.0",
    "eslint-plugin-jsx-a11y": "^6.6.1",
    "eslint-plugin-react": "^7.31.10",
    "eslint-plugin-react-hooks": "^4.6.0",
    "typescript": "^4.8.4",
}
const { t } = useTranslation('footer');

            <div>
              <Link to="/terms-conditions">{t('links.terms-conditions')}</Link>
              <Link to="/privacy-policy">{t('links.privacy-policy')}</Link>
            </div>
This t() usage type error:

Type 'DefaultTFuncReturn' is not assignable to type 'ReactI18NextChild | Iterable<ReactI18NextChild>'.ts(2322) index.d.ts(47, 5): The expected type comes from property 'children' which is declared here on type 'IntrinsicAttributes & LinkProps & RefAttributes<HTMLAnchorElement>'

However, I can see relevant type definitions that should allow this. Similar error is noticed with general JSX tags:
  const { t } = useTranslation(['login', 'errors']);

        <LoginHeader>
          <h1 className={style.login__title}>{t('login:signin.title')}</h1>
          <p className={style.login__paragraph}>{t('login:signin.subtitle')}</p>
        </LoginHeader>
Type 'DefaultTFuncReturn' is not assignable to type 'ReactI18NextChild | Iterable<ReactI18NextChild>'.ts(2322) index.d.ts(47, 5): The expected type comes from property 'children' which is declared here on type 'DetailedHTMLProps<HTMLAttributes<HTMLHeadingElement>, HTMLHeadingElement>'

I've already tried to remove package-lock.json and node_modules to have a clean install, but it didn't help.

I'm running into the same issue with the versions mentioned above, have you found any solutions yet ?

Oh, I found a solutions for it, just downgrade react-i18next to version 11.18.6 and it'll solve the issue. Seems like the issue is with version 12

ivansvlv · 2022-10-21T13:18:12Z

@fitimbyttyqi thanks, that helped indeed. Version ^11.18.6 works fine.

cjsilva-umich · 2022-10-24T18:15:46Z

Would be great if this could be looked into so that version 12 could be used without this error

imransilvake · 2022-10-25T14:51:55Z

working with ^11.18.6
problem with ^12.0.0

ben-lawlor-k · 2022-10-26T11:07:15Z

I also had the same error when applying TypeScript in i18n.

Type 'TFunctionResult' is not assignable to type 'ReactNode'.
  Type 'object' is not assignable to type 'ReactNode'.
    Type '{}' is missing the following properties from type 'ReactPortal': key, children, type, propsts(2322)

So I modified it as follows.

{t("base.content.no")}
=> {t<string>("base.content.no")}

or

{t("brand.button.management")}
=> {`${t("brand.button.management")}`}

This works with react-i18next ^12.0.0

Tautorn · 2022-10-26T18:26:17Z

working with ^11.18.6 problem with ^12.0.0

It works for me. Thank you.

I did update to version 12.0.0 and it generated the error. Was it necessary a downgrade version.

imransilvake · 2022-10-26T20:18:19Z

working with ^11.18.6 problem with ^12.0.0

It works for me. Thank you.

I did update to version 12.0.0 and it generated the error. Was it necessary a downgrade version.

Yes until there is a standard fix from the team.

pedrodurek · 2022-10-26T20:23:53Z

This PR will fix that, there is only one small downside that I'll describe there.

adrai · 2022-10-27T07:54:06Z

can you try with i18next v22.0.3?

ben-lawlor-k · 2022-10-27T08:28:24Z

can you try with i18next v22.0.3?

Working with i18next v22.0.3 and react-i18next v12.0.0. Thank you!

gHashTag · 2022-11-12T18:14:41Z

the following versions work for me

"i18next": "22.0.4",
"react-i18next": "12.0.0",

nick4fake · 2022-11-13T19:00:00Z

@gHashTag I have same versions, it doesn't work

adrai · 2022-11-13T19:01:40Z

and with i18next v22.0.5?

nick4fake · 2022-11-13T19:10:15Z

@adrai Exactly the same error after updating to 22.0.5

nick4fake · 2022-11-13T19:36:40Z

@adrai I am really sorry, apparently I've had it cached. 22.0.5 works! Thanks

EnvyIT · 2022-11-29T08:58:43Z

@adrai this issues should be re-open. it still is a problem with:

"i18next": "^22.0.6",
"react": "18.2.0",
"react-i18next": "^12.0.0",


"typescript": "^4.9.3",

Leads to TS error : TS2322: Type 'DefaultTFuncReturn' is not assignable to type 'string | undefined'. Type 'null' is not assignable to type 'string | undefined'.

When can you provide a fix that is working as expected?

adrai · 2022-11-29T09:00:26Z

@adrai this issues should be re-opned. it still is a problem with:
"i18next": "^22.0.6",
"react": "18.2.0",
"react-i18next": "^12.0.0",


"typescript": "^4.9.3",
Leads to TS error : TS2322: Type 'DefaultTFuncReturn' is not assignable to type 'string | undefined'. Type 'null' is not assignable to type 'string | undefined'.

When can you provide a fix that is working as expeced?

@EnvyIT you have a different issue: https://www.i18next.com/overview/typescript#argument-of-type-defaulttfuncreturn-is-not-assignable-to-parameter-of-type-xyz

EnvyIT · 2022-11-29T09:05:05Z

Well , you are right @adrai thanks for your fast response. Was this introduced in a specific version? I am curious because in 21.8.10 it is working perfectly fine.

adrai · 2022-11-29T09:06:12Z

Well , you are right @adrai thanks for your fast response. Was this introduced in a specific version? I am curious because in 21.8.10 it is working perfectly fine.

Yes, in the last major v22

kirillleogky · 2022-11-29T14:20:05Z

"next": "^12.3.0",
"next-i18next": "^13.0.0",
"react": "17.0.2",
"react-i18next": "^12.0.0",
"i18next": "^22.0.6",

my next-i18next.config.js:

module.exports = {
  i18n: {
    locales: ['en'],
    defaultLocale: 'en',
  },
};

inside app:


import { useTranslation } from 'react-i18next';
....
const [label, setLabel] = useState('');
const { t } = useTranslation();
...
setLabel(t('common:continue'));

I don't get where I need to put returnNull: false,

adrai · 2022-11-29T14:24:27Z


"next": "^12.3.0",

"next-i18next": "^13.0.0",

"react": "17.0.2",

"react-i18next": "^12.0.0",

"i18next": "^22.0.6",

my next-i18next.config.js:


module.exports = {

  i18n: {

    locales: ['en'],

    defaultLocale: 'en',

  },

};

inside app:




import { useTranslation } from 'react-i18next';

....

const [label, setLabel] = useState('');

const { t } = useTranslation();

...

setLabel(t('common:continue'));

I don't get where I need to put returnNull: false,

module.exports = {
  i18n: {
    locales: ['en'],
    defaultLocale: 'en',
  },
  returnNull: false,
};

kirillleogky · 2022-11-29T15:31:39Z


"next": "^12.3.0",

"next-i18next": "^13.0.0",

"react": "17.0.2",

"react-i18next": "^12.0.0",

"i18next": "^22.0.6",

my next-i18next.config.js:


module.exports = {

  i18n: {

    locales: ['en'],

    defaultLocale: 'en',

  },

};

inside app:




import { useTranslation } from 'react-i18next';

....

const [label, setLabel] = useState('');

const { t } = useTranslation();

...

setLabel(t('common:continue'));

I don't get where I need to put returnNull: false,

module.exports = {
  i18n: {
    locales: ['en'],
    defaultLocale: 'en',
  },
  returnNull: false,
};

still the same
i even re-install modules but nothing

maybe smth wrong inside next.config.js

/** @type {import('next').NextConfig} */
const { i18n } = require('./next-i18next.config');
const withPWA = require('next-pwa');

const nextConfig = {
  i18n,
  // Due to Material UI styles mismatch
  reactStrictMode: false,
  fallback: true,
  images: {
    loader: 'custom',
  },

  compiler: {
    emotion: true,
  },

  pwa: {
    dest: 'public',
    swSrc: 'service-worker.js',
    disable: process.env.NODE_ENV === 'development',
    // cacheOnFrontEndNav: true,
    fallbacks: {
      image: '/assets/default-image.png',
    },
  },

  publicRuntimeConfig: {
......
  },

  serverRuntimeConfig: {
....
  },

  webpack(config) {
    config.module.rules.push({
      test: /\.svg$/,
      use: ['@svgr/webpack'],
    });

    return config;
  },

  async redirects() {
    return [
      {
        source: '/admin',
        destination: '/admin/performance',
        permanent: true,
      },
      {
        source: '/creator',
        destination: '/creator/episodes',
        permanent: true,
      },
    ];
  },
};

module.exports = withPWA(nextConfig);

adrai · 2022-11-29T15:39:08Z

@kirillleogky did you also set returnNull in the i18next.d.ts file?

// i18next.d.ts
import 'i18next';

declare module 'i18next' {
  interface CustomTypeOptions {
    returnNull: false;
    ...
  }
}

If so, please create a minimal reproducible example and open a new issue.

zhrivodkin · 2023-02-09T05:59:44Z

import { useTranslation } from 'next-i18next';
const { t } = useTranslation(['layout']);
...
<Button size="xs" kind="secondary">
  {t('signup_submit')}
</Button>

package.json:

"i18next": "^22.4.9",
"next": "^13.1.5",
"next-i18next": "^13.1.4",
"react-i18next": "^12.1.5"

Still not working.

adrai · 2023-02-09T06:05:21Z

@zhrivodkin did you try: https://www.i18next.com/overview/typescript#argument-of-type-defaulttfuncreturn-is-not-assignable-to-parameter-of-type-xyz ?

zhrivodkin · 2023-02-09T08:46:50Z

@zhrivodkin did you try: https://www.i18next.com/overview/typescript#argument-of-type-defaulttfuncreturn-is-not-assignable-to-parameter-of-type-xyz ?

Oh, thank you so much! Among the waterfall of comments I did not see the solution.

mleister97 · 2023-03-14T09:43:14Z

Still didn't get it running. The solution did not work. Any updates?

FranciscoOssian · 2023-05-18T22:52:48Z

It may not necessarily be a bug, but somehow it ends up causing a problem. Ideally, the function should return a string with a fallback value.

const { t: translation, i18n } = useTranslation();
const t = (s: string) => translation<string>(s);

I went with this approach so I don't have to make changes throughout the entire file. By the way, I'm migrating the code to ts, and this issue hasn't come up before.

IberaSoft · 2023-05-19T06:51:06Z

A potential solution could be:

<div>{t<string>('your-label')}</div>

or

<div>{${t('your-label')}}</div>

voliva · 2023-05-22T13:08:19Z

I've used the following patch, and it seems to be working fine:

diff --git a/node_modules/i18next/index.d.ts b/node_modules/i18next/index.d.ts
index e7b769d..045e4e1 100644
--- a/node_modules/i18next/index.d.ts
+++ b/node_modules/i18next/index.d.ts
@@ -690,6 +690,13 @@ export type TFunctionResult =
 export type TFunctionKeys = string | TemplateStringsArray;
 export interface TFunction {
   // basic usage
+  <
+    TKeys extends TFunctionKeys = string,
+    TInterpolationMap extends object = StringMap,
+  >(
+    key: TKeys | TKeys[],
+    options?: TOptions<TInterpolationMap> | string,
+  ): string;
   <
     TResult extends TFunctionResult = string,
     TKeys extends TFunctionKeys = string,

I've just added an overload that returns a simple string, which is what's mostly expected when using the TFunction.

HT-Moh closed this as completed Apr 14, 2022

alishaz-polymath mentioned this issue May 19, 2022

Fix: Dynamic link dark mode color calcom/cal.com#2821

Merged

5 tasks

marcoXbresciani pushed a commit to marcoXbresciani/TKCompanionApp that referenced this issue Jun 10, 2022

Fix I18N warnings

2dc5888

See i18next/next-i18next#1795 (comment)

polaroidkidd mentioned this issue Jul 14, 2022

move worker availability request to rtk query LibrePhotos/librephotos-frontend#73

Merged

MarcelGeo mentioned this issue Oct 7, 2022

withTranslation - Type error: Type 'TFunctionResult' is not assignable to type 'ReactNode' i18next/react-i18next#1559

Closed

jaywcjlove mentioned this issue Oct 22, 2022

Type 'DefaultTFuncReturn' is not assignable to type 'ReactI18NextChild | Iterable<ReactI18NextChild>' jaywcjlove/tools#38

Closed

pedrodurek mentioned this issue Oct 27, 2022

Omit object from t function i18next/i18next#1858

Merged

7 tasks

adrai closed this as completed Oct 27, 2022

adrai mentioned this issue Dec 13, 2022

Consider setting the default for returnNull to false in next major version (v23.0.0) i18next/i18next#1884

Closed

14 tasks

betelgeuseAS mentioned this issue Oct 16, 2023

Configure i18next betelgeuseAS/imagery#21

Closed

Type error: Type 'TFunctionResult' is not assignable to type 'ReactNode'. #1795

Type error: Type 'TFunctionResult' is not assignable to type 'ReactNode'. #1795

Comments

HT-Moh commented Apr 13, 2022

Describe the bug

Occurs in next-i18next version

Steps to reproduce

Expected behaviour

Screenshots

Additional context

Solution

HT-Moh commented Apr 14, 2022 • edited

azuken commented May 2, 2022 • edited

quertenmont commented May 5, 2022

qjnz commented May 5, 2022

MouzamSadiq commented May 11, 2022

phankietit commented May 22, 2022

adriandmitroca commented May 25, 2022

bedcoding commented May 30, 2022 • edited

marcoXbresciani commented Jun 10, 2022

keremcanb commented Jun 15, 2022 • edited

Shackey666 commented Jul 8, 2022 • edited

HT-Moh commented Jul 14, 2022

sigespweb22 commented Sep 9, 2022

Dam998 commented Sep 20, 2022

layerok commented Sep 21, 2022

MarcelGeo commented Oct 7, 2022

OnkelTem commented Oct 9, 2022 • edited

OnkelTem commented Oct 9, 2022

ivansvlv commented Oct 21, 2022

fitimbytyqi commented Oct 21, 2022 • edited

ivansvlv commented Oct 21, 2022

cjsilva-umich commented Oct 24, 2022

imransilvake commented Oct 25, 2022 • edited

ben-lawlor-k commented Oct 26, 2022

Tautorn commented Oct 26, 2022

imransilvake commented Oct 26, 2022

pedrodurek commented Oct 26, 2022

adrai commented Oct 27, 2022

ben-lawlor-k commented Oct 27, 2022

gHashTag commented Nov 12, 2022

nick4fake commented Nov 13, 2022

adrai commented Nov 13, 2022

nick4fake commented Nov 13, 2022

nick4fake commented Nov 13, 2022

EnvyIT commented Nov 29, 2022 • edited

adrai commented Nov 29, 2022

EnvyIT commented Nov 29, 2022

adrai commented Nov 29, 2022

kirillleogky commented Nov 29, 2022

adrai commented Nov 29, 2022

kirillleogky commented Nov 29, 2022

adrai commented Nov 29, 2022 • edited

zhrivodkin commented Feb 9, 2023

adrai commented Feb 9, 2023

zhrivodkin commented Feb 9, 2023

mleister97 commented Mar 14, 2023

FranciscoOssian commented May 18, 2023

IberaSoft commented May 19, 2023

voliva commented May 22, 2023

HT-Moh commented Apr 14, 2022 •

edited

azuken commented May 2, 2022 •

edited

bedcoding commented May 30, 2022 •

edited

keremcanb commented Jun 15, 2022 •

edited

Shackey666 commented Jul 8, 2022 •

edited

OnkelTem commented Oct 9, 2022 •

edited

fitimbytyqi commented Oct 21, 2022 •

edited

imransilvake commented Oct 25, 2022 •

edited

EnvyIT commented Nov 29, 2022 •

edited

adrai commented Nov 29, 2022 •

edited