Skip to content

Conversation

ENCRYPTEDFOREVER
Copy link
Contributor

No description provided.

@ENCRYPTEDFOREVER
Copy link
Contributor Author

@kravetsone could you please check for regressions

@kravetsone
Copy link

kravetsone commented Apr 12, 2025

@kravetsone could you please check for regressions

PS Z:\PROJECTS\Gcargo run --package gh-pages-generator --bin gh-pages-generator -- dev
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.24s
     Running `target\debug\gh-pages-generator.exe dev`
Error: Parser: Integer parsing: invalid digit found in string

Caused by:
    0: Integer parsing: invalid digit found in string
    1: invalid digit found in string
error: process didn't exit successfully: `target\debug\gh-pages-generator.exe dev` (exit code: 1)
PS Z:\PROJECTS\GRAMIO\types\tg-bot-api> git branch
* bot_api_9_0

@ENCRYPTEDFOREVER
Copy link
Contributor Author

ENCRYPTEDFOREVER commented Apr 12, 2025

> Error: Parser: Integer parsing: invalid digit found in string
> 
> Caused by:
>     0: Integer parsing: invalid digit found in string
>     1: invalid digit found in string

Sorry I somehow deleted that part fix and didn't notice when cleaning up before committing yesterday 😅
Should be good now

@kravetsone
Copy link

kravetsone commented Apr 13, 2025

Mostly fine but #26 ... oh telegram

@ENCRYPTEDFOREVER
Copy link
Contributor Author

ENCRYPTEDFOREVER commented Apr 13, 2025

Mostly fine but #26 ... oh telegram

Oh yea I noticed that problem, tho it's not so trivial to implement generally...
For this PR the main goal is to not break something that worked previously, did you notice anything?
Parts of the schema which I use personally seem fine, but I don't use the entire schema, so I'm not sure

kravetsone added a commit to gramiojs/types that referenced this pull request Apr 13, 2025
@kravetsone
Copy link

In my opinion, everything is fine) Thanks for the fix! I was already struggling with my realization, but parsing natural language is quite difficult...

https://github.com/gramiojs/schema-parser

so i will do it later...

@kravetsone
Copy link

gramiojs/types@v8.3.3...v9.0.0

you can see changes with you fix here (but it typescript types)

@ENCRYPTEDFOREVER
Copy link
Contributor Author

gramiojs/types@v8.3.3...v9.0.0

you can see changes with you fix here (but it typescript types)

🫠 😄

@LasterAlex
Copy link

Hello! I am a contributor to the teloxide crate, and we recently became up to date with the TBA! I'm looking at a way to check our hand-written schema.ron, and this project looks quite promising. Is there any way I could help get this PR and maybe 9.1 merged and ready?

@kravetsone
Copy link

Hello! I am a contributor to the teloxide crate, and we recently became up to date with the TBA! I'm looking at a way to check our hand-written schema.ron, and this project looks quite promising. Is there any way I could help get this PR and maybe 9.1 merged and ready?

You can use this branch 9.1 generated without problems
The project purpose is to generate schema so just do it

https://github.com/gramiojs/types/releases

@LasterAlex
Copy link

Alright, thanks a lot!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants