-
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
[BUG] example project fails to generate code #346
Comments
@vipw woah it's nice catch. could you share your swagger file name? |
It's using the default swagger files from the example.
I think the files are downloaded to |
@vipw thanks! Swaggers from urls is pretty new feature. I will try to fix it asap |
@vipw Looks like problem in slashes. I am working on macOS machine. Will check it on my Windows laptop |
Experiencing issues with slashes on windows, everything above version 2.3.13 is not working. |
@ByronHolt yes yes, the main priority for us - to fix Windows for now |
Hi @ByronHolt I've fixed your issue, but lost phone and cannot sign in with two factor auth at weekend. Today evening I will push changes and close this issue. Thanks for waiting. |
* Downgraded path dependency * Updated pubspec and changelog * Fixed enums with 'class' name generation #283 * Fixed names duplication * Fixed case when class named 'Query' #343 * Updated pubspec and changelog * Fixed _dateToJson generation destination when separateModels=true #347 * Fixed #350 * Updated pubspec and changelog * Updated changelog and pubspec * Updated changelog description * One more update * Fix #346 * Updated changelog Co-authored-by: uladzimir_paliukhovich <>
Describe the bug
With a fresh checkout of this project (d272376), the example fails to generate code.
To Reproduce
cd to the example subdirectory and run:
flutter pub get
flutter pub run build_runner build --delete-conflicting-outputs
Expected behavior
Classes to be generated for the swagger petstore example.
Library version used:
d272376
Additional context
The code that's being generated has paths in the
export
Output:
The text was updated successfully, but these errors were encountered: