feat: improve performance of response data parsing #1173
Annotations
10 errors and 1 warning
Run npm run lint:
src/metadata-parser.ts#L379
Property 'streamBuffer' does not exist on type 'Parser'. Did you mean 'readBuffer'?
|
Run npm run lint:
src/token/colmetadata-token-parser.ts#L93
Property 'streamBuffer' does not exist on type 'Parser'. Did you mean 'readBuffer'?
|
Run npm run lint:
src/token/colmetadata-token-parser.ts#L114
Property 'streamBuffer' does not exist on type 'Parser'. Did you mean 'readBuffer'?
|
Run npm run lint:
src/token/nbcrow-token-parser.ts#L26
Property 'streamBuffer' does not exist on type 'Parser'. Did you mean 'readBuffer'?
|
Run npm run lint:
src/token/nbcrow-token-parser.ts#L52
Property 'suspended' does not exist on type 'Parser'. Did you mean 'suspend'?
|
Run npm run lint:
src/token/nbcrow-token-parser.ts#L53
Property 'streamBuffer' does not exist on type 'Parser'. Did you mean 'readBuffer'?
|
Run npm run lint:
src/token/nbcrow-token-parser.ts#L55
Property 'suspended' does not exist on type 'Parser'. Did you mean 'suspend'?
|
Run npm run lint:
src/token/nbcrow-token-parser.ts#L56
Property 'next' does not exist on type 'Parser'.
|
Run npm run lint:
src/token/returnvalue-token-parser.ts#L33
Property 'streamBuffer' does not exist on type 'Parser'. Did you mean 'readBuffer'?
|
Run npm run lint:
src/token/returnvalue-token-parser.ts#L66
Property 'streamBuffer' does not exist on type 'Parser'. Did you mean 'readBuffer'?
|
Determine npm cache directory
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
The logs for this run have expired and are no longer available.
Loading