fromPartial method returns an error,'Argument type {} is not assignable to parameter type I'

[zsp419]

With the tool's automatically generated code, the fromPartial method returns an error, as shown below:

here is my protofile code:

please help me!

[stephenh]

Hi @zsp419 , that code has not caused issues in the past; out of curiosity, what version of TypeScript are you using? I'm wondering if it's a TS 5.x behavior.

[Truman55]

same problem. TS 5.0.4

[zsp419]

what ide do you use,I had problems with IntelliJ IDEA before, but vscode is fine

[stephenh]

Fwiw I've bumped ts-proto's integration tests to TypeScript 5.1 and am not getting any errors from the ?? {} lines. And I'm using Webstorm.

We have a useExactTypes=false flag that might avoid this error, but also would be great to find out what specifically is causing this. Like a tsconfig setting?

Granted we could always add a {} as any to get around it, but would be nice to know more about why this is not working.

[TennyZhuang]

Same error on ts 5.1.6

My tsconfig is normal:

{
  "compilerOptions": {
    "target": "es6",
    "lib": [
      "dom",
      "dom.iterable",
      "esnext"
    ],
    "allowJs": true,
    "skipLibCheck": true,
    "strict": true,
    "forceConsistentCasingInFileNames": true,
    "noEmit": true,
    "esModuleInterop": true,
    "module": "esnext",
    "moduleResolution": "node",
    "resolveJsonModule": true,
    "isolatedModules": true,
    "jsx": "preserve",
    "incremental": true,
  },
  "include": [
    "next-env.d.ts",
    "**/*.ts",
    "**/*.tsx"
  ],
  "exclude": [
    "node_modules"
  ]
}

[stephenh]

I pushed a fix that adds an as any on that line. Fwiw my guess is that non-trivial protobuf schemas cause issues with our useExactTypes flag, so I recommend turning it off if you see these issues.

[stephenh]

🎉 This issue has been resolved in version 1.156.2 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release
• v1.156.2

Your semantic-release bot 📦🚀