Open eunchurn opened 1 year ago
Hi! π
Firstly, thanks for your work on this project! π
Today I used patch-package to patch @types/forge-apis@0.8.3 for the project I'm working on.
@types/forge-apis@0.8.3
Here is the diff that solved my problem:
diff --git a/node_modules/@types/forge-apis/index.d.ts b/node_modules/@types/forge-apis/index.d.ts index b48e3db..0391f11 100755 --- a/node_modules/@types/forge-apis/index.d.ts +++ b/node_modules/@types/forge-apis/index.d.ts @@ -166,7 +166,7 @@ export interface JobPayloadInput { export interface JobObjOutputPayloadAdvanced { exportFileStructure?: string | undefined; modelGuid?: string | undefined; - objectIds?: string[] | undefined; + objectIds?: number[] | undefined; } export interface JobPayloadItem {
This issue body was partially generated by patch-package.
https://github.com/Autodesk-Forge/forge-api-nodejs-client/blob/master/docs/JobObjOutputPayloadAdvanced.md
its string[] not num[] as defined in docs
Document was wrong. Actually string array was not accepted. By using API.
Hi! π
Firstly, thanks for your work on this project! π
Today I used patch-package to patch
@types/forge-apis@0.8.3
for the project I'm working on.Here is the diff that solved my problem:
This issue body was partially generated by patch-package.