-
Notifications
You must be signed in to change notification settings - Fork 124
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[QUESTION] Chooper 4.x.x? #248
Comments
Hi @masseelch , We're not using chopper to generate our code. You can use latest version of our generator and latest version of chopper at the same time. Where did you found chopper 3.x version? Please find our our example https://github.com/epam-cross-platform-lab/swagger-dart-code-generator/blob/master/example/pubspec.yaml So because we already support null-safe version, I'm not going to update Readme. It's fine? |
Chopper started to use null-safety with version 4.0.0. With the constraints given in the current readme the user will not get 4.0.x but the not null-safe version 3.0.6. I did not know I can use the generator without generating chopper. This works for me :-) |
The example does not compile though 😢
|
@masseelch did you find out why example not compiles? Any questions? |
No I did not look any further. I think I won't use this package. There are some things, that bother me, to be honest:
|
Okay, my fault: my IDE removed the
|
Part of my spec: "responses": {
"400": {
"description": "invalid input, data invalid",
"content": {
"application/json": {
"schema": {
"type": "object",
"properties": {
"code": {
"type": "integer",
"format": "int32",
"example": 400
},
"errors": {
"type": "object",
"properties": {}
},
"status": {
"type": "string",
"example": "Bad Request"
}
}
}
}
}
}, The above is valid OAS 3.0.3 schema. Will you accept a PR prefixing numeric names with an |
@masseelch , Ahh, looks like your swagger file has some border cases. I'm reopening the issue. Can you swagger code for at least one model with such name? I will fix it ASAP. Will try to do this today. |
I am using this one |
@masseelch thanks, I will try to handle it soon. Will let you know. |
Thank you very much 🥰 |
Hi again @masseelch , |
You are awesome ❤️ |
Can confirm, build runs green. I will now checkout the generated code. Awesome work! |
* Fix #248 * Updated changelog and pubspec * Added ability to include or exclude paths * Fixed ability to set exclude_path and include_path Co-authored-by: uladzimir_paliukhovich <>
Please describe a problem.
I am wondering: Current published version is flaged as nullsafe but is using a non-nullsafe version of chopper (3.x) while there already is a published nullsafe version (4.x).
Describe the solution you'd like
Clarify whether 4.x is supported and if so update the readme.
The text was updated successfully, but these errors were encountered: