fix(tl): correctly process vector<bytes>
fml why am i even doing this
This commit is contained in:
parent
fa8ed6da10
commit
02462dac16
3 changed files with 3 additions and 3 deletions
|
@ -2,9 +2,9 @@ import { TlEntry } from './types'
|
||||||
|
|
||||||
function normalizeType(s: string): string {
|
function normalizeType(s: string): string {
|
||||||
return s
|
return s
|
||||||
|
.replace(/^bytes/, 'string')
|
||||||
.replace(/</g, ' ')
|
.replace(/</g, ' ')
|
||||||
.replace(/>/g, '')
|
.replace(/>/g, '')
|
||||||
.replace('bytes', 'string')
|
|
||||||
.replace('int53', 'long')
|
.replace('int53', 'long')
|
||||||
}
|
}
|
||||||
|
|
||||||
|
|
|
@ -2,7 +2,7 @@
|
||||||
|
|
||||||
> TL schema and related utils used for MTCute.
|
> TL schema and related utils used for MTCute.
|
||||||
|
|
||||||
Generated from TL layer **142** (last updated on 14.05.2022).
|
Generated from TL layer **142** (last updated on 30.05.2022).
|
||||||
|
|
||||||
## About
|
## About
|
||||||
|
|
||||||
|
|
File diff suppressed because one or more lines are too long
Loading…
Reference in a new issue